Operational trust controls for MCP adoption
TrustOps answers which MCP servers agents are allowed to use, keeps that decision fresh, alerts when risk changes, and exports the result into runtimes, gateways, CI, and admin review.
/v1/decide/v1/route/v1/ledger/evidence-pack/v1/mandatesPlatform modules
Verify Registry, Cloud, Gateway, Ledger, and Mandates share one trust model: server evidence, policy, user authorization, runtime context, and audit proof stay linked.
Fresh trusted index
Buyer decisions should default to fresh, confidence-weighted evidence. Long-tail servers remain searchable, but stale or never-validated scores are visibly separated from servers that meet a freshness SLA.
/healthz/routesAuthenticated validation is premium
Public validation is free. Paid authenticated validation lets publishers provide test credentials, run authorized tool calls, verify scopes per tool, detect overbroad scopes, and prove write-action confirmation flows.
Freshness tiers
| Tier | SLA | Priority revalidation |
|---|---|---|
| Community | 720h | |
| Pro | 168h | |
| Enterprise | 24h |
Plans
Demo flow
Alerting
Watch servers, categories, shortlists, or team inventories and trigger email, Slack, Teams, webhook, RSS, GitHub issue, or PagerDuty-style routes.
Buyer paths
APIs and MCP tools
/v1/trustops/capabilities/v1/servers/{namespace}/{name}/trustops/v1/servers/{namespace}/{name}/policyroute_task decide_agent_call create_mandate get_evidence_pack compile_docs export_policy get_subscription_options get_gateway_options get_hosting_optionsPOST /v1/decidePOST /v1/mandatesGET /v1/ledger/evidence-packPOST /v1/docs/compile