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-22T17:46:37.945207+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://demo.mobcrm.au/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T17:46:37.945207+00:00",
"registry_status": null,
"subject": {
"id": "io.github.benkaiser/mob-demo",
"kind": "mcp"
},
"tools": {
"names": [
"activity_list",
"activity_manage",
"activity_type_manage",
"address_manage",
"batch_create_activities",
"batch_create_contacts",
"batch_tag_contacts",
"contact_create",
"contact_delete",
"contact_find_duplicates",
"contact_get",
"contact_list",
"contact_merge",
"contact_method_manage",
"contact_restore",
"contact_timeline",
"contact_update",
"contacts_needing_attention",
"custom_field_manage",
"data_export",
"data_statistics",
"debt_manage",
"food_preferences_get",
"food_preferences_upsert",
"gift_list",
"gift_manage",
"global_search",
"life_event_manage",
"manage_push_notifications",
"manage_settings",
"note_list",
"note_manage",
"notification_create",
"notification_list",
"notification_read",
"prime",
"relationship_manage",
"reminder_manage",
"tag_manage",
"task_manage",
"upcoming_birthdays",
"upcoming_reminders"
],
"names_truncated": false,
"sha256": "49dee0b26d8713c4bdadff62c5803f98c835d741d3f7927e890835a82a79a549"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T17:46:37.945207+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