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-22T02:37:07.985119+00:00 · State: partial
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": "partial",
"endpoint": "https://aaaa-nexus.atomadictech.workers.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T02:37:07.985119+00:00",
"registry_status": null,
"subject": {
"id": "x402/ecosystem:-add-aaaa-nexus-\u2014-hosted-ai-infrastructure-with-x4",
"kind": "mcp"
},
"tools": {
"names": [
"aegis_mcp_proxy_execute",
"aegis_router_epistemic_bound",
"agents_plan",
"authorize_action",
"certify_codebase",
"certify_output",
"contract_verify",
"docs_generate",
"entitlement_attest",
"federation_mint",
"forge_audit",
"forge_certify",
"forge_recon",
"forge_tier_infer",
"forge_wire",
"hallucination_oracle",
"identity_verify",
"intent_classify",
"keys_validate",
"lineage_record",
"lint_analyze",
"omega_emit_materialize",
"omega_emit_polyglot",
"omega_intent_nl",
"omega_intent_route",
"rag_augment",
"ratchet_register",
"rng_quantum",
"spending_authorize",
"sys_constants",
"sys_lint_gate",
"sys_trust_gate",
"text_summarize",
"threat_score",
"uep_aha_detect",
"uep_autopoiesis_plan",
"uep_context",
"uep_preflight",
"uep_synthesis_guard",
"uep_trace_certify",
"vanguard_continuous_redteam",
"vanguard_escrow_lock_and_verify",
"vanguard_mev_route_intent",
"vanguard_wallet_govern_session"
],
"names_truncated": false,
"sha256": "dc9b6d876f5c3a7d3ac389032e78379ef5317aad71cc5adf8324a8cfce6440b6"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T02:37:07.985119+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