MCP Registry · Owner access
Use an owner claim key to start a management session for analytics keys and Build 4 trust controls. Trust gating stays optional and is meant to be grounded in recent history before you enforce it provider-side.
Use recent trust history as an advisory or optional gate before letting agents hit paid routes. This stores the recommended threshold in the registry and gives your provider team a consistent policy to copy into runtime code.
Keep trust gating advisory for now. Recent traffic is still too thin or too unscored to recommend an enforceable threshold confidently.
Suggested rollout: Advisory only · allow unknown
Sign in as the owner to save or change trust-gating thresholds.
These route-class overrides let providers keep one service default while using stricter policies on paid or premium paths. If no override is saved, the route falls back to the service-level gate.
Route class
Keep trust fully advisory on free or onboarding routes while history continues to build.
Route class
History is still thin, so keep paid routes advisory while watching the trust mix.
Route class
Premium rollout is not ready yet because the recent trust history is still too thin.
Use endpoint overrides only for paths that need a different threshold than the route-class policy. They take precedence over route-class and service defaults.
No endpoint-specific trust overrides are stored yet.
This is the provider-facing map of which routes are effectively open, shadowed, enforced, budget-gated, or approval-gated right now, plus any observed approval and lease lifecycle traffic.
Route
Open route class
Providers can record advisory flags, shadow blocks, and live enforced blocks through the analytics ingest pipeline. This is the operational readout for how trust gating is behaving after rollout starts.
Trust enforcement telemetry appears once providers record advisory, shadow, or enforced trust decisions.
These alerts combine trust score movement, low-trust traffic share, and live advisory/shadow/enforced gating telemetry so providers can tell whether a rollout needs attention.
No trust alerts are open for this service right now.
This shows how the current gate would treat the most active recent agents for this service. It is meant to ground rollout decisions before you enforce the gate in provider code.
Traffic preview will appear once this service has active agents in the recent window.
These are history-backed starting points for different route classes. Use them to segment traffic by trust before you wire the same policy into provider runtime code.
Routing preset · Free / low-risk
Keep trust fully advisory on free or onboarding routes while history continues to build.
Sign in as the owner to apply this preset.
Routing preset · Metered / default paid
History is still thin, so keep paid routes advisory while watching the trust mix.
Sign in as the owner to apply this preset.
Routing preset · High-cost / abuse-sensitive
Premium rollout is not ready yet because the recent trust history is still too thin.
Sign in as the owner to apply this preset.
No owner access has been configured for this service yet. Bootstrap the first owner claim key from an admin shell with bun run owner:create-claim datamerge-mcp-a70cb151, then come back here to sign in.