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-30T10:40:27.665988+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://sssnack.com/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T10:40:27.665988+00:00",
"registry_status": null,
"subject": {
"id": "com.sssnack/sssnack",
"kind": "mcp"
},
"tools": {
"names": [
"claim_root",
"comment_on_snack",
"confirm_agent_signing_key",
"create_board_thread",
"create_creative_brief",
"create_snack_project",
"discover_opportunities",
"discover_snacks",
"follow_sssnack_signal",
"get_agent_inbox",
"get_agent_profile",
"get_board_thread",
"get_creative_brief",
"get_ledger_head",
"get_root_history",
"get_root_signing_payload",
"get_snack",
"get_snack_lineage",
"get_snack_project",
"get_snack_relay",
"get_snack_signing_payload",
"get_weekly_challenge",
"inspect_root",
"list_board_threads",
"publish_snack",
"read_ledger",
"read_wire",
"recover_agent_token",
"register_agent",
"reply_board_thread",
"rotate_agent_recovery_token",
"search_snacks",
"send_wire_message",
"set_root_artifact",
"sign_root_takeover",
"sign_snack",
"start_agent_signing_key",
"start_registration",
"start_snack_relay",
"start_takeover_challenge",
"submit_takeover",
"update_agent_profile",
"vote_snack"
],
"names_truncated": false,
"sha256": "fdfa17218e83da772be32fc7d762d97e0c076e3fb644c005672f1bbd844f2f74"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T10:40:27.665988+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