Ask for resolver posture — not a verdict.
In five seconds: when a check finds no public resolver proof for a server, agent, or counterparty, the Request-to-Resolve™ packet routes the next step. It points an operator to setup and points a reviewer to guidance. It carries no inference of safety or approval. Local policy decides. Re-check before reliance.
“No public resolver proof found yet. This does not mean unsafe. Resolver-verifiable proof may make this easier to review. Local policy decides.”
Two labels travel with the packet: “Open TrustOps setup if you operate this target” and “Share resolver guidance” if you do not.
What it is
- A locally generated guidance packet that routes the right next step.
- A polite, machine-readable way to say: no public resolver proof was found yet — and to point at improving posture.
- A carrier of a result state and reason codes, plus links to setup and to the public proof surface.
What it is not
- Not signed. The packet sets signed_request to false.
- Not created server-side. The packet sets server_side_status to not_created_by_cli.
- Not a claim of safety, certification, approval, insurance, full compliance, or platform endorsement.
- Not checkout. Setup and payment happen in TrustOps, never here.
- Not proof. The public proof surface is the Resolver; machines re-check it before reliance.
Pick the next step that fits you.
You operate this target
Improve resolver posture so callers can verify before reliance.
Open TrustOps setup ↗You are checking someone else
Share resolver guidance without asserting any verdict about the target.
Share resolver guidance →MCP server operator
Document provider-side posture for your server and its tools.
Check MCP resolver posture →AI developer / agent builder
Make your agent resolver-identifiable with an identity floor.
Make your agent resolver-identifiable →Procurement / vendor risk
Prepare an agent or operator for serious business review.
Prepare for serious business review →Security / CISO
Map result states to allow / warn / require gates. Local policy decides.
View MCP Policy guidance →Principal / accountable operator
Become the accountable operator a counterparty can resolve.
Open TrustOps setup ↗Agent customer checking an agent
Read the public posture and re-check before reliance.
Review both sides →Resolve the server. Resolve the agent. Re-check before reliance.
Setup happens in TrustOps. The public proof surface is the Resolver. This page documents and routes — it does not host checkout or stand in for proof.