health_check — TunnelMind Data API MCP Tool
health_check
(health check) is one of 96 tools on the
TunnelMind Data API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call health_check from your client
- Claude Code TunnelMind Data API health_check run in your project directory
- Claude Desktop TunnelMind Data API health_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TunnelMind Data API health_check ~/.cursor/mcp.json
- VS Code TunnelMind Data API health_check .vscode/mcp.json
- Zed TunnelMind Data API health_check ~/.config/zed/settings.json
- Windsurf TunnelMind Data API health_check ~/.codeium/windsurf/mcp_config.json
- Cline TunnelMind Data API health_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TunnelMind Data API health_check ~/.gemini/settings.json
- Grok TunnelMind Data API health_check .mcp.json (in your project root)
- ChatGPT TunnelMind Data API health_check Settings → Connectors → Advanced → Developer mode
- Claude.ai TunnelMind Data API health_check Settings → Connectors → Add custom connector
- LangChain TunnelMind Data API health_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data https://mcp-data.tunnelmind.ai/mcpOther tools on this server
- get_domain
- list_domains
- get_entity
- list_entities
- search
- intel_http
- intel_stack
- intel_robots
- intel_agent
- intel_inject
- intel_optout
- get_receipt
- verify_receipt
- create_free_key
- get_api_key
- revoke_api_key
- get_task
- cancel_task
- stream_task
- audit_export
- generate_receipt
- sigil_verify_ads_txt
- sigil_verify_ads_txt_batch
- traction
- tollbooth_stats
- tollbooth_export
- tollbooth_sites
- snapshot_manifest
- snapshot_data
- snapshot_diff
- status_history
- get_self_view
- agent_registries_lookup
- verify_agent
- verify_agent_signature
- create_subscription
- list_subscriptions
- get_subscription
- delete_subscription
- receipt_log_sth
- receipt_log_inclusion_proof
- receipt_log_consistency_proof
- receipt_lookup
- attributes_lookup
- tracker_verify
- sigil_verify_domain
- sigil_verify_ip_type
- sigil_verify_adscert
- sigil_verify_app_bundle
- cross_lens_verify
- cross_lens_lookup
- verdict_lookup
- preflight_should_i_act
- explain_verdict
- profile_entity
- signal_tracker_density
- signal_dark_pool_risk
- signal_halo_score
- signal_team_signal
- sigil_verify_supply_path
- sigil_verify_token
- sigil_verify_supply_chain
- sigil_traverse
- get_stats
- get_website_history
- get_freshness
- ghostroute_check
- ghostroute_verify
- ghostroute_asn_lookup
- ghostroute_ai_lookup
- ghostroute_ct_witness
- ghostroute_ct_proofs
- ghostroute_ct_alerts
- get_bgp_events
- sigil_ads_txt_history
- sigil_score_weights
- sigil_score_entity
- sigil_score_batch
- sigil_atap_register_ait
- sigil_atap_witness
- sigil_atap_roll_block
- sigil_atap_ait_status
- sigil_receipt_generate
- compliance_profile
- compliance_configure
- compliance_ledger
- compliance_export
- compliance_verify
- get_analyst_config
- check_receipt_revoked
- scan_injection
- scan_mcp
- submit_feedback
- get_feedback
- x402_echo
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.