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-20T13:43:51.517964+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-data.tunnelmind.ai/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T13:43:51.517964+00:00",
"registry_status": null,
"subject": {
"id": "ai.tunnelmind/data",
"kind": "mcp"
},
"tools": {
"names": [
"agent_registries_lookup",
"attributes_lookup",
"audit_export",
"cancel_task",
"check_receipt_revoked",
"compliance_configure",
"compliance_export",
"compliance_ledger",
"compliance_profile",
"compliance_verify",
"create_free_key",
"create_subscription",
"cross_lens_lookup",
"cross_lens_verify",
"delete_subscription",
"explain_verdict",
"generate_receipt",
"get_analyst_config",
"get_api_key",
"get_bgp_events",
"get_changes",
"get_demand_aggregate",
"get_domain",
"get_entity",
"get_feedback",
"get_freshness",
"get_pricing",
"get_receipt",
"get_referral",
"get_referral_log",
"get_self_view",
"get_stats",
"get_subscription",
"get_task",
"get_tool_registry",
"get_website_history",
"ghostroute_ai_lookup",
"ghostroute_asn_lookup",
"ghostroute_batch_check",
"ghostroute_cert_lookup",
"ghostroute_check",
"ghostroute_ct_alerts",
"ghostroute_ct_proofs",
"ghostroute_ct_witness",
"ghostroute_verify",
"health_check",
"intel_agent",
"intel_http",
"intel_inject",
"intel_optout",
"intel_robots",
"intel_stack",
"list_domains",
"list_entities",
"list_subscriptions",
"preflight_should_i_act",
"profile_entity",
"receipt_log_consistency_proof",
"receipt_log_inclusion_proof",
"receipt_log_sth",
"receipt_lookup",
"revoke_api_key",
"scan_injection",
"scan_mcp",
"search",
"sigil_ads_txt_history",
"sigil_atap_ait_status",
"sigil_atap_register_ait",
"sigil_atap_roll_block",
"sigil_atap_witness",
"sigil_receipt_generate",
"sigil_score_batch",
"sigil_score_entity",
"sigil_score_weights",
"sigil_traverse",
"sigil_verify_ads_txt",
"sigil_verify_ads_txt_batch",
"sigil_verify_adscert",
"sigil_verify_app_bundle",
"sigil_verify_domain",
"sigil_verify_ip_type",
"sigil_verify_supply_chain",
"sigil_verify_supply_path",
"sigil_verify_token",
"signal_dark_pool_risk",
"signal_halo_score",
"signal_team_signal",
"signal_tracker_density",
"snapshot_data",
"snapshot_diff",
"snapshot_manifest",
"status_history",
"stream_task",
"submit_feedback",
"tollbooth_export",
"tollbooth_sites",
"tollbooth_stats",
"tracker_verify",
"traction",
"verdict_lookup"
],
"names_truncated": true,
"sha256": "a517b99a3e38e8d6e3b90e08f453bce8e669df79837ac5174ad99df057a75592"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T13:43:51.517964+00:00",
"version": "1.0.0"
}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