For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-21T17:43:19.237574+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://baton-mcp-production.up.railway.app/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T17:43:19.237574+00:00",
"registry_status": null,
"subject": {
"id": "io.github.vinsenzo83/baton",
"kind": "mcp"
},
"tools": {
"names": [
"baton_account",
"baton_agent_list",
"baton_agent_record_result",
"baton_agent_register",
"baton_approve",
"baton_close_room",
"baton_confirm_payment",
"baton_consolidate",
"baton_cost_record",
"baton_cost_summary",
"baton_create_room",
"baton_diff",
"baton_git_evidence",
"baton_git_record",
"baton_hub_list",
"baton_hub_observe",
"baton_hub_register",
"baton_inbox",
"baton_join",
"baton_kick",
"baton_leave",
"baton_memory_delete",
"baton_memory_get",
"baton_memory_put",
"baton_memory_search",
"baton_new_invite",
"baton_pass",
"baton_receive",
"baton_revoke",
"baton_send",
"baton_signup",
"baton_task_create",
"baton_task_graph",
"baton_task_link",
"baton_task_update",
"baton_upgrade",
"baton_verify",
"baton_verify_plan",
"baton_who",
"spider_checklist",
"spider_classify_tier",
"spider_plan",
"spider_pull_corpus",
"spider_record_pattern",
"spider_signals"
],
"names_truncated": false,
"sha256": "a2a31ae37813db9f692d26649d11c395f5f3457a3497de841266dc8c219b548f"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T17:43:19.237574+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology