Home / MCP registry index / ai.tunnelmind/data

TunnelMind Data API

ai.tunnelmind/data in the official MCP registry. Endpoint https://mcp-data.tunnelmind.ai/mcp.

The registry describes it as: Tracker / Sigil / Cross-lens — every TunnelMind Data API operation as one MCP surface.

We read its 104 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http data https://mcp-data.tunnelmind.ai/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "data": {
      "url": "https://mcp-data.tunnelmind.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"data","type":"http","url":"https://mcp-data.tunnelmind.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

health_check 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 and 44 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/ai-tunnelmind-data/badge.svg)](https://lazaretto.dev/mcp-registry/ai-tunnelmind-data)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.