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:03:33.201950+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://x402-compute.68cxgfyr0.workers.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T02:03:33.201950+00:00",
"registry_status": null,
"subject": {
"id": "io.github.kali123411/k402",
"kind": "mcp"
},
"tools": {
"names": [
"attest_verify",
"catalog",
"channel_config",
"channel_status",
"classify",
"covenant_address",
"covenant_broadcast",
"covenant_build",
"covenant_check",
"covenant_compile",
"covenant_utxos",
"embed_text",
"extract",
"generate",
"job_result",
"job_status",
"kaspa_balance",
"kaspa_fee_estimate",
"kaspa_network",
"kaspa_tx_status",
"kaspa_utxos",
"open_session",
"pay_per_call",
"payment_options",
"prove_guest_upload",
"prove_preflight",
"prove_submit",
"read_url",
"registry_provider",
"registry_search",
"rewrite",
"search_index",
"search_query",
"session_status",
"summarize",
"use_session"
],
"names_truncated": false,
"sha256": "37d11370521589fd53223a05668284cedb4ab9d6656a87d490f45df6790523d9"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T02:03:33.201950+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