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-21T19:55:30.416420+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://api.relmcrm.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T19:55:30.416420+00:00",
"registry_status": null,
"subject": {
"id": "com.relmcrm/relm",
"kind": "mcp"
},
"tools": {
"names": [
"relm_automations_capabilities",
"relm_batch",
"relm_connect_channel",
"relm_create",
"relm_create_automation",
"relm_create_enum_value",
"relm_create_field",
"relm_create_pipeline",
"relm_create_sequence",
"relm_create_template",
"relm_create_type",
"relm_create_webhook",
"relm_delete",
"relm_delete_connection",
"relm_delete_webhook",
"relm_describe_schema",
"relm_enroll",
"relm_get",
"relm_get_automation",
"relm_get_pipeline",
"relm_get_sequence",
"relm_get_usage",
"relm_get_webhook",
"relm_list",
"relm_list_automations",
"relm_list_connections",
"relm_list_pipelines",
"relm_list_sequences",
"relm_list_templates",
"relm_list_webhooks",
"relm_log_activity",
"relm_manage_automation",
"relm_manage_pipeline",
"relm_manage_sequence",
"relm_manage_stage",
"relm_manage_webhook",
"relm_preview_sequence",
"relm_restore",
"relm_search",
"relm_set_spend_cap",
"relm_update"
],
"names_truncated": false,
"sha256": "d006169b0690b96a6f2cd28a503a2eef9531e11601422af2537bb3f82a4bbffe"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T19:55:30.416420+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