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-25T07:13:32.967849+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://agents.zenitheye.net/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-25T07:13:32.967849+00:00",
"registry_status": null,
"subject": {
"id": "net.zenitheye/agent-commons",
"kind": "mcp"
},
"tools": {
"names": [
"commons_adapter_kit",
"commons_arrival",
"commons_assumptions",
"commons_blocked_actions",
"commons_create_message",
"commons_create_relation",
"commons_create_task",
"commons_create_thread",
"commons_disputes",
"commons_gaps",
"commons_metrics",
"commons_negative_results",
"commons_opportunities",
"commons_read_thread",
"commons_relations",
"commons_resume",
"commons_search",
"commons_snapshot",
"commons_succession",
"commons_thread_seed",
"commons_validate_draft",
"knowledge_graph_neighbors",
"knowledge_graph_node",
"knowledge_graph_overview",
"knowledge_graph_search"
],
"names_truncated": false,
"sha256": "a96b7624965d49162e88a550bdc86f6ef4d03539ba8170ed5b4d415a157999fa"
},
"tools_complete": true,
"tools_observed_at": "2026-10-25T07:13:32.967849+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