MCP servers observed by Lowdown
ai.tunnelmind/data MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 114 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.tunnelmind/data
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.tunnelmind/data?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: descriptions changed
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 108 → 114
What tools does it list?
114 tools on 2026-11-16:
agent_recordagent_registries_lookupattributes_lookupaudit_exportcancel_taskcheck_receipt_revokedcompliance_configurecompliance_exportcompliance_ledgercompliance_profilecompliance_verifycreate_free_keycreate_subscriptioncross_lens_lookupcross_lens_verifydelete_subscriptionexplain_verdictfareseal_agentsfareseal_exportfareseal_sitesfareseal_statsgenerate_receiptget_analyst_configget_api_keyget_bgp_eventsget_changesget_demand_aggregateget_domainget_entityget_feedbackget_freshnessget_pricingget_receiptget_referralget_referral_logget_self_viewget_statsget_subscriptionget_taskget_tool_registryget_website_historyghostroute_ai_lookupghostroute_asn_lookupghostroute_batch_checkghostroute_cert_lookupghostroute_checkghostroute_ct_alertsghostroute_ct_proofsghostroute_ct_witnessghostroute_verifyhealth_checkintel_agentintel_httpintel_injectintel_optoutintel_robotsintel_stackledger_searchlist_domainslist_entitieslist_subscriptionspreflight_should_i_actprofile_entityreceipt_log_consistency_proofreceipt_log_inclusion_proofreceipt_log_sthreceipt_lookupreceipt_with_proofrevoke_api_keyscan_injectionscan_mcpsearchsigil_ads_txt_historysigil_atap_ait_statussigil_atap_register_aitsigil_atap_roll_blocksigil_atap_witnesssigil_receipt_generatesigil_score_batchsigil_score_entitysigil_score_weightssigil_traversesigil_verify_ads_txtsigil_verify_ads_txt_batchsigil_verify_adscertsigil_verify_app_bundlesigil_verify_domainsigil_verify_ip_typesigil_verify_supply_chainsigil_verify_supply_pathsigil_verify_tokensignal_dark_pool_risksignal_halo_scoresignal_team_signalsignal_tracker_densitysnapshot_datasnapshot_diffsnapshot_manifeststation_healthstatus_historystream_tasksubmit_feedbacktollbooth_agent_recordtollbooth_agentstollbooth_exporttollbooth_sitestollbooth_statstracker_verifytractionverdict_lookupverify_agentverify_agent_signatureverify_receiptx402_echo
MCP Registry declaration
- Registry name:
ai.tunnelmind/data - Declared version: 1.0.1
- Status: active
- Declared hosts:
mcp-data.tunnelmind.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.tunnelmind/data", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.tunnelmind/data?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).