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-22T01:30:56.214040+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://agentdata-api.sander-van-aard.workers.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T01:30:56.214040+00:00",
"registry_status": null,
"subject": {
"id": "io.github.darthsander/agentdata-nl",
"kind": "mcp"
},
"tools": {
"names": [
"attest_settlement",
"check_ch_company",
"check_crypto_firm",
"check_crypto_signal",
"check_cz_company",
"check_dutch_insolvency",
"check_fi_company",
"check_fr_company",
"check_fr_insolvency",
"check_no_company",
"check_pl_company",
"check_token_registry",
"check_uk_company",
"check_x402_counterparty",
"crypto_feed_since",
"crypto_feed_subscribe",
"crypto_track_record",
"crypto_verdict",
"doc_extract",
"doc_ocr",
"doc_to_markdown",
"eurc_peg",
"file_agent_want",
"get_crypto_evidence",
"get_crypto_signal",
"llm_chat",
"lookup_lei",
"media_transcribe",
"news_search",
"preflight_x402_service",
"relay_crypto_news",
"relay_edgar_filings",
"relay_reddit_search",
"request_capability",
"scan_crypto_market",
"screen_dutch_supplier",
"screen_eu_sanctions",
"screen_eu_supplier",
"validate_crypto_signal",
"verify_eu_vat",
"web_contents",
"web_crawl",
"web_images",
"web_places",
"web_scholar",
"web_search",
"web_search_read",
"x402_demand_report",
"x402_network_feed_check",
"x402_network_feed_since",
"x402_network_feed_subscribe",
"x402_network_report",
"x402_service_report"
],
"names_truncated": false,
"sha256": "f1efbd8494703c649f218d22fdcabadfbfcd69139304f2189e8158e4552df516"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T01:30:56.214040+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