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:34:36.867895+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://satoshidata.ai/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T02:34:36.867895+00:00",
"registry_status": null,
"subject": {
"id": "x402/add-satoshidata.ai-to-ecosystem-\u2014-bitcoin-chain-intelligence",
"kind": "mcp"
},
"tools": {
"names": [
"address_evidence_pack",
"address_intelligence",
"address_risk",
"batch_intelligence",
"batch_risk_signals",
"batch_summary",
"batch_trust_safety",
"bitcoin_price",
"block_detail",
"chain_awakenings",
"dormancy_flushes",
"entity_categories",
"entity_list",
"entity_lookup",
"entity_recent_activity",
"fees_recommended",
"mempool_stats",
"mempool_stress",
"mempool_tx",
"mining_pool_info",
"network_intelligence",
"onchain_stats",
"op_return_decode",
"pool_detail",
"pool_list",
"pulse_consolidations",
"pulse_dormant",
"pulse_summary",
"pulse_whales",
"risk_check",
"risk_check_batch",
"submit_feedback",
"timestamp_hash",
"timestamp_quote",
"tx_broadcast",
"tx_status",
"tx_verify",
"verify_timestamp",
"wallet_contributors",
"wallet_detail",
"wallet_flow_graph",
"wallet_summary",
"wallet_trust_safety",
"whale_alerts"
],
"names_truncated": false,
"sha256": "7a8dd5aa507696b2e1ae8eed08a41ad92a86310dc16ead22def59d08ab78c403"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T02:34:36.867895+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