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-22T19:47:56.929772+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://mcp.chainhelix.io/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T19:47:56.929772+00:00",
"registry_status": null,
"subject": {
"id": "io.chainhelix/intel",
"kind": "mcp"
},
"tools": {
"names": [
"agent_report",
"agent_standing",
"attest",
"attest_spec",
"attest_status",
"attestation_stats",
"bridge_flows",
"btc_mempool_history",
"builder_relays",
"buy_key",
"buyer_clearance",
"candles",
"chain_brief",
"claim_key",
"cleared_buyer",
"congestion",
"correlation_matrix",
"daily_digest",
"data_changelog",
"deep_report",
"delivery_spec",
"delivery_status",
"fill_receipts",
"freshness",
"gas_state",
"governance_activity",
"hire_plan_gridtrader",
"hire_plan_healthmon",
"hire_plan_rebalancer",
"hire_plan_yieldopt",
"hire_quote",
"instrument_signals",
"instrument_spec",
"instrument_state",
"instruments",
"iv_summary",
"key_order_status",
"latest_signals",
"lead_alert_spec",
"lead_alerts",
"lexicon_bulk",
"lexicon_bundle",
"lexicon_resolve",
"lexicon_spec",
"lexicon_statement",
"liquidations",
"list_attestations",
"list_reveals",
"market_state",
"mev_bots",
"mev_flow_spec",
"mev_intel",
"mev_pool_check",
"mev_pressure",
"open_interest",
"options_skew",
"prices",
"proof_spec",
"receipt_spec",
"screened_payer",
"search_agents",
"session_stats",
"situation_report",
"stablecoin_flows",
"standing_bulk",
"standing_spec",
"standing_watch",
"stream_register",
"stream_register_all",
"verified_agents",
"verified_delivery",
"verify_fill",
"verify_instrument_signal",
"verify_lead_alert",
"verify_reveal",
"victim_flow",
"wall_map",
"wallet_risk",
"webhook_register",
"webhook_status",
"webhook_unregister",
"whale_flows"
],
"names_truncated": false,
"sha256": "d531c0081c8d4a1a04d4f5e33b43a1cccfbd10cb6a857a168958afeb9989fec3"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T19:47:56.929772+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