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-21T00:07:21.006923+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://catalyst.stratogenic.ai/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T00:07:21.006923+00:00",
"registry_status": null,
"subject": {
"id": "io.github.stratogenic-ai/catalyst",
"kind": "mcp"
},
"tools": {
"names": [
"catalyst_accept_proposals",
"catalyst_activate_compliance_framework",
"catalyst_await_approval",
"catalyst_bulk_update_tasks",
"catalyst_check_action",
"catalyst_create_tasks_from_findings",
"catalyst_decline_proposals",
"catalyst_evaluate_agent_action",
"catalyst_export_ledger",
"catalyst_export_workflow_audit",
"catalyst_get_compliance_findings",
"catalyst_get_dashboard",
"catalyst_get_graph_views",
"catalyst_get_org_summary",
"catalyst_get_workflow_trust",
"catalyst_ingest_task",
"catalyst_list_compliance_frameworks",
"catalyst_list_compliance_rules",
"catalyst_list_proposals",
"catalyst_log_task",
"catalyst_my_governance",
"catalyst_pending_approvals",
"catalyst_register_approval_webhook",
"catalyst_register_machine_actor",
"catalyst_register_workflow",
"catalyst_review_proposal",
"catalyst_run_compliance_scan",
"catalyst_search_tasks",
"catalyst_send_lite_event",
"catalyst_update_task",
"catalyst_weekly_summary"
],
"names_truncated": false,
"sha256": "5625988a780c0fb7d3e808a994d5f9e199fe993a00540783968b0a575c8dd6a2"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T00:07:21.006923+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