← Back to search
MCP TRUSTOPS

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.

Runtime decision API
/v1/route
Recommend a server, allow read tools, block risky tools, and require approval for write actions.
Policy exports
JSON, Rego, YAML
Also exports GitHub Action, gateway config, and client readiness reports.
Publisher wedge
Claim + Verify
Verified owners get priority revalidation, badges, monitoring, and authenticated validation workflows.
Private registry
Internal MCP inventory
Scan private endpoints and repos, rank internal tools, and export workspace allowlists.

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.

Fresh evidence
Prioritize servers validated within the configured freshness window.
Long-tail inventory
Keep discoverability without treating old evidence as a production decision.
Synthetic route checks
/healthz/routes
Rankings, shortlists, RSS, Healthcare, ChatGPT-compatible, and Claude-compatible pages are probed for render stability.

Authenticated 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.

Publisher setup
Claim → Plan → Credentials
The management page accepts verified claim tokens, plan selection, alert watches, and scheduled authenticated credentials.
TrustOps gate
tier-enforced
Authenticated credential storage requires the configured TrustOps feature tier.

Freshness tiers

TierSLAPriority revalidation
Community 720h
Pro 168h
Enterprise 24h

Plans

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 flow

Step 1
Vet an MCP server
Open the report, read the executive verdict, and separate client compatibility from production trust.
Step 2
Export policy
Generate JSON, Rego, YAML, CI, or gateway rules from the same evidence.
Step 3
Route an agent task
Use /v1/route to allow safe read tools, block risky writes, and require approval where needed.
Step 4
Subscribe to alerts
Watch the server, category, shortlist, or private inventory for score, schema, auth, and freshness changes.

Alerting

Watch servers, categories, shortlists, or team inventories and trigger email, Slack, Teams, webhook, RSS, GitHub issue, or PagerDuty-style routes.

Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

Buyer paths

PLATFORM TEAMS
Rank and route agents to MCP tools with fresh trust scores, policy exports, and runtime decisioning.
AI ADMINS
Approve MCP apps before employees use them, monitor drift, and export enforceable policy.
PUBLISHERS
Improve your score, prove ownership, run priority revalidation, and publish trust badges.
SECURITY
Detect risky agent tools before deployment and separate security probes from product analytics.
MARKETPLACES
Use Verify scores, readiness, freshness, and policy data through stable registry APIs.

APIs and MCP tools

Capabilities
/v1/trustops/capabilities
Server profile
/v1/servers/{namespace}/{name}/trustops
Policy
/v1/servers/{namespace}/{name}/policy
MCP tools
route_task export_policy get_subscription_options