MCP TrustOps for MCP publishers

Improve your score, prove ownership, run priority revalidation, and publish trust badges.

Audience

MCP publishers

Primary API

/v1/servers/{namespace}/{name}/claims

Policy exports

JSON, Rego, YAML, CI

Use cases

Claim server ownership through GitHub, DNS, or HTTP challenge.
Run authenticated validation and semantic benchmarks with maintainer-provided access.
Embed freshness, OAuth, write-safe, enterprise-ready, and supply-chain badges.

Proof points

Owner pages expose claim, revalidate, badge, and monitoring steps on every server.
Badge metadata includes embeddable Markdown and public badge SVG URLs.
Maintainer annotations document expected behavior, releases, incidents, and rebuttals.

Sample flow

Flow

claim ownership -> revalidate -> publish badge

Sample output

{
  "claim_status": "verified",
  "next_action": "run authenticated validation",
  "badge": "Verified by MCP Verify",
  "monitoring": ["freshness", "score", "write_surface"]
}

Related buyer paths

Agent platform teams Enterprise AI admins Security teams MCP marketplaces