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:00:36.361996+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.agent4.io/v1/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T17:00:36.361996+00:00",
"registry_status": null,
"subject": {
"id": "io.agent4/agent4-tenant",
"kind": "mcp"
},
"tools": {
"names": [
"add_knowledge_file",
"add_knowledge_text",
"build_knowledge_index",
"clone_storyline",
"configure_share",
"create_agent",
"create_knowledge_base",
"create_share",
"create_skill",
"create_storyline",
"diagnose_prompt",
"export_storyline",
"get_agent",
"get_end_user",
"get_knowledge_base",
"get_knowledge_index",
"get_skill",
"get_storyline",
"import_storyline",
"improve_prompt",
"list_agents",
"list_end_users",
"list_knowledge_bases",
"list_mcp_servers",
"list_page_contexts",
"list_shares",
"list_skills",
"list_storylines",
"list_tools",
"list_user_sessions",
"page_context_stats",
"patch_knowledge_index",
"preview_plan",
"publish_storyline",
"resolve_page_context",
"search_agent4_docs",
"search_knowledge_base",
"set_custom_domain",
"set_pwa_branding",
"tenant_info",
"test_planner_trigger",
"test_skill_trigger",
"unpublish_storyline",
"update_agent",
"update_knowledge_base",
"update_skill",
"update_storyline",
"upsert_page_context",
"usage_stats",
"validate_storyline"
],
"names_truncated": false,
"sha256": "b19fca5e1cd2681017146eefbb60d4cca2fc0c10e97e2dd1b52a30ca399f96df"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T17:00:36.361996+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