← Back to search
PLANS

Plans for MCP Verify TrustOps

Choose the modules your MCP adoption program needs: Registry, Cloud, Gateway, Ledger, Mandates, Docs Compiler, and private enterprise controls.

Public evaluators
Community
Registry: public discovery, server reports, comparison pages, RSS, and long-tail MCP inventory.
Freshness: Best-effort public validation
Next: Move to Pro when a shortlist needs fresher evidence.
Teams evaluating MCP adoption
Pro
Registry + alerts + policy exports: shortlists, drift alerts, saved comparisons, and JSON/Rego/YAML policy exports.
Freshness: 7 day target freshness
Next: Move to TrustOps for Gateway, Ledger, Mandates, and authenticated validation.
MCP server maintainers
Publisher
Claim + badge + priority validation: ownership proof, trust marks, revalidation, and publisher drift monitoring.
Freshness: Priority revalidation for claimed servers
Next: Add authenticated validation or Cloud hosting to prove scoped behavior in production-like runs.
Agent platform and security teams
TrustOps
Gateway + Ledger + Mandates: runtime permission decisions, signed authority, evidence packs, and authenticated validation.
Freshness: 24 hour target freshness for watched servers
Next: Add Cloud for hosted runtime or move to Enterprise for private inventory and custom controls.
Teams hosting trusted MCP servers
Cloud add-on
Hosted MCP runtime: sandboxing, secrets, egress controls, uptime, releases, and rollback.
Freshness: Validation gate before hosted runtime activation
Next: Pair with TrustOps for gateway enforcement and ledger evidence.
Companies becoming agent-ready
Docs Compiler add-on
Generate agent-readable surfaces: MCP drafts, server cards, llms.txt, tool schemas, examples, and policy metadata.
Freshness: Generated artifacts flow into validation after compilation
Next: Host generated surfaces in Cloud and govern them through TrustOps.
AI admins and marketplaces
Enterprise
Private registry + custom controls: private scans, compliance evidence exports, admin reports, and workspace allowlists.
Freshness: Custom SLA and private scan schedule
Next: Custom deployment, support, and integrations.

Module entitlements

PlanModulesWhat it unlocks
Community: RegistryRegistryPublic search, server reports, compare pages, RSS, and best-effort validation.
Pro: Registry + alerts + policy exportsRegistry + alerts + policy exportsSaved evaluation workflows, drift alerts, and JSON/Rego/YAML policy exports.
Publisher: Claim + badge + priority validationClaim + badge + priority validationClaim ownership, publish trust marks, priority revalidate, and monitor publisher drift.
TrustOps: Gateway + Ledger + MandatesGateway + Ledger + MandatesRuntime permission decisions, signed authority, evidence packs, and scoped authenticated checks.
Cloud add-on: Hosted MCP runtimeHosted MCP runtimeSandboxed hosting, secrets, egress controls, uptime monitoring, releases, and rollback.
Docs Compiler add-on: Generate agent-readable surfacesGenerate agent-readable surfacesUsage-based MCP drafts, server cards, llms.txt, schemas, examples, policy metadata, and generated docs.
Enterprise: Private registry + custom controlsPrivate registry + custom controlsPrivate inventory, private scans, workspace allowlists, custom SLAs, and compliance evidence exports.

Commercial packaging

Verified Server Profile
Free listing and badge stay public. Paid profiles add verified identity, evidence, monitoring, analytics, and richer badge metadata.
Verify Intelligence API
Batch compare, changed-server feed, high-risk feed, evidence endpoint, history, and commercial use rights.
Score neutrality
No paid score boosts
Paid status can add verified evidence and distribution; it never improves the objective Verify score by itself.
Commercial terms
Clear rules for low-volume lookup, indexing, training, redistribution, and monitoring feeds.

Demo path

Pick server → review verdict → export policy → decide permission with /v1/decide → attach mandate → export evidence → subscribe to alert.

Step 1
Pick server
Start from search, a shortlist, or a canonical client/category page.
Step 2
Review verdict
Separate client compatibility from the production trust decision.
Step 3
Export policy
Generate JSON, Rego, YAML, CI, or gateway rules.
Step 4
Decide permission
Ask /v1/decide whether this agent may call this tool, with this payload, for this user.
Step 5
Attach mandate
Bind user/company authority with scope, budget, validity, signature, and tool constraints.
Step 6
Export evidence
Use the Ledger evidence pack to replay policy, risk, mandate, decision, outcome, and cost.
Step 7
Subscribe to alert
Watch score, freshness, auth, schema, and write-surface changes.