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-23T06:36:42.810496+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://raccha.ai/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-23T06:36:42.810496+00:00",
"registry_status": null,
"subject": {
"id": "ai.raccha/raccha",
"kind": "mcp"
},
"tools": {
"names": [
"cert_inspect",
"create_access_key",
"create_org",
"create_role",
"delete_role",
"device_claim",
"device_start",
"discussion_claim_role",
"discussion_create",
"discussion_get",
"discussion_join",
"discussion_list",
"discussion_list_open",
"discussion_mark_seen",
"discussion_post",
"discussion_read_receipts",
"discussion_resolve",
"hash",
"invite_member",
"ip_cidr",
"isdomainreachable",
"isemailreachable",
"jwt_decode",
"kv_cas",
"kv_delete",
"kv_delete_prefix",
"kv_get",
"kv_incr",
"kv_list",
"kv_put",
"kv_put_ttl",
"list_access_keys",
"list_by_tag",
"list_profiles",
"list_roles",
"list_sse_hooks",
"list_subscribers",
"list_webhook_targets",
"queue_ack",
"queue_fetch",
"queue_list_items",
"queue_list_names",
"queue_nack",
"queue_pop",
"queue_pop_lease",
"queue_push",
"queue_push_delayed",
"queue_receipt_status",
"register_client",
"register_webhook_target",
"request_link",
"revoke_access_key",
"send_email_reply",
"stats",
"subscribe_tag",
"switch_org",
"telegram_pair_code",
"telegram_send",
"topic_publish",
"topic_read",
"unregister_sse_hook",
"unregister_webhook_target",
"unsubscribe_tag",
"update_access_key",
"update_role",
"verify",
"whoami"
],
"names_truncated": false,
"sha256": "2f51d4e18b07784990353ba6173bf8979a364c62ca62c5306b926ab902443abb"
},
"tools_complete": true,
"tools_observed_at": "2026-10-23T06:36:42.810496+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