Plans for MCP Verify TrustOps

Choose how much freshness, policy automation, publisher proof, and private inventory your MCP adoption program needs.

Public evaluators

Community

Search, compare, public reports, RSS, and long-tail discovery.

Freshness: Best-effort public validation

Next: Move to Pro when a shortlist needs fresher evidence.

Teams evaluating MCP adoption

Pro

Freshness-focused shortlists, saved comparisons, policy exports, and alert watches.

Freshness: 7 day target freshness

Next: Move to TrustOps for runtime routing and authenticated validation.

MCP server maintainers

Publisher

Claim ownership, priority revalidate, publish badges, and configure monitoring.

Freshness: Priority revalidation for claimed servers

Next: Add authenticated validation to prove scoped behavior.

Agent platform and security teams

TrustOps

Authenticated validation, freshness SLAs, alert routing, policy exports, and runtime decisions.

Freshness: 24 hour target freshness for watched servers

Next: Move to Enterprise for private inventory and custom controls.

AI admins and marketplaces

Enterprise

Private registry ingestion, internal scans, admin reports, and workspace allowlists.

Freshness: Custom SLA and private scan schedule

Next: Custom deployment, support, and integrations.

Demo path

Pick server → review verdict → export policy → route task → 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

Route task

Ask /v1/route which tools are allowed, blocked, or approval-gated.

Step 5

Subscribe to alert

Watch score, freshness, auth, schema, and write-surface changes.