Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LiveDataLink

REMOTE · LIVEDATALINK.AI

294 public-data tools across 60 domains; source freshness varies. Free tier.

Available components

+3 this week 84 Trust /100

Last scanned (1 hour ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 57975 tokens (~152/item across 381 items; 381 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 381 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 382 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 4 Nov 26 +3
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 3 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 2 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 1 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 31 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 30 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 29 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://livedatalink.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=livedatalink.ai CN=WE1,O=Google Trust Services,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 1dc254398a8befce13ca447b1564d73e
SANs: livedatalink.ai, *.livedatalink.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of livedatalink.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
livedatalink.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://livedatalink.ai/mcp Verified 200
http (plaintext) http://livedatalink.ai/mcp HTTPS enforced 301 https://livedatalink.ai/mcp
MCP tools · 381 exposed · ~57,819 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cve_search_by_keyword ~94

No description provided.

NameTypeReqDescription
keywordstringyes–
limitnumber––
pub_end_datestring––
pub_start_datestring––

No output schema declared.

No examples provided.

cve_search_by_vendor ~128

No description provided.

NameTypeReqDescription
limitnumber––
productstring––
pub_end_datestring––
pub_start_datestring––
vendorstringyes–

No output schema declared.

No examples provided.

cwe_lookup ~58

No description provided.

NameTypeReqDescription
cwe_idstringyes–

No output schema declared.

No examples provided.

disaster_declarations ~176

No description provided.

NameTypeReqDescription
countystring––
end_datestring––
incident_typestring––
limitnumber––
start_datestring––
statestring––

No output schema declared.

No examples provided.

disaster_history_summary ~79

No description provided.

NameTypeReqDescription
countystring––
statestringyes–
yearsnumber––

No output schema declared.

No examples provided.

disaster_recovery_profile ~359

No description provided.

NameTypeReqDescription
addressstring––
areastringyes–
countystring––
statestring––

No output schema declared.

No examples provided.

earthquake_recent ~192

No description provided.

NameTypeReqDescription
end_timestring––
latnumber––
limitnumber––
locationstring––
lonnumber––
min_magnitudenumber––
radius_kmnumber––
start_timestring––

No output schema declared.

No examples provided.

edgar_company_facts ~141

No description provided.

NameTypeReqDescription
conceptstring––
identifierstringyes–
taxonomystring––

No output schema declared.

No examples provided.

edgar_company_lookup ~94

No description provided.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

edgar_filing_content ~133

No description provided.

NameTypeReqDescription
accession_numberstringyes–
cikstringyes–
max_charsinteger––

No output schema declared.

No examples provided.

edgar_filings_by_form_type ~139

No description provided.

NameTypeReqDescription
form_typestringyes–
limitinteger––
start_datestring––

No output schema declared.

No examples provided.

edgar_full_text_search ~146

No description provided.

NameTypeReqDescription
end_datestring––
formsstring––
limitinteger––
querystringyes–
start_datestring––

No output schema declared.

No examples provided.

edgar_insider_transactions ~76

No description provided.

NameTypeReqDescription
identifierstringyes–
limitinteger––

No output schema declared.

No examples provided.

edgar_recent_filings ~148

No description provided.

NameTypeReqDescription
form_typestring––
identifierstringyes–
limitinteger––
start_datestring––

No output schema declared.

No examples provided.

eia_electricity_state ~218

No description provided.

NameTypeReqDescription
endstring––
limitinteger––
metricstring––
sectorstring––
startstring––
statestring––

No output schema declared.

No examples provided.

eia_energy_consumption ~153

No description provided.

NameTypeReqDescription
endstring––
limitinteger––
sectorstring––
startstring––
statestring––

No output schema declared.

No examples provided.

eia_gasoline_prices ~183

No description provided.

NameTypeReqDescription
endstring––
gradestring––
limitinteger––
regionstring––
startstring––

No output schema declared.

No examples provided.

eia_natural_gas ~154

No description provided.

NameTypeReqDescription
endstring––
limitinteger––
seriesstring––
startstring––

No output schema declared.

No examples provided.

eia_oil_supply ~184

No description provided.

NameTypeReqDescription
endstring––
limitinteger––
metricstring––
regionstring––
startstring––

No output schema declared.

No examples provided.

eia_renewable_generation ~173

No description provided.

NameTypeReqDescription
endstring––
limitinteger––
sourcestring––
startstring––
statestring––

No output schema declared.

No examples provided.

eia_series_lookup ~177

No description provided.

NameTypeReqDescription
endstring––
limitinteger––
series_idstringyes–
startstring––

No output schema declared.

No examples provided.

energy_market_snapshot ~175

No description provided.

NameTypeReqDescription
lookback_daysinteger––

No output schema declared.

No examples provided.

entity_dossier ~173

No description provided.

NameTypeReqDescription
limitinteger––
namestringyes–
statestring––

No output schema declared.

No examples provided.

entity_resolve ~138

No description provided.

NameTypeReqDescription
namestringyes–
statestring––

No output schema declared.

No examples provided.

environmental_site_risk ~271

No description provided.

NameTypeReqDescription
addressstring––
sitestringyes–
statestring––

No output schema declared.

No examples provided.

epa_enforcement_search ~91

No description provided.

NameTypeReqDescription
registry_idstringyes–

No output schema declared.

No examples provided.

epa_facility_compliance ~109

No description provided.

NameTypeReqDescription
registry_idstringyes–

No output schema declared.

No examples provided.

epa_facility_details ~100

No description provided.

NameTypeReqDescription
registry_idstringyes–

No output schema declared.

No examples provided.

epa_facility_search ~229

No description provided.

NameTypeReqDescription
active_onlyboolean––
citystring––
limitinteger––
namestring––
statestring––
zipstring––

No output schema declared.

No examples provided.

epa_water_or_air_violations ~124

No description provided.

NameTypeReqDescription
mediastring––
registry_idstringyes–

No output schema declared.

No examples provided.

epss_score ~52

No description provided.

NameTypeReqDescription
cve_idstringyes–

No output schema declared.

No examples provided.

faa_public_aviation_airport_profile ~175

No description provided.

NameTypeReqDescription
airportstringyes–
response_formatstring––

No output schema declared.

No examples provided.

faa_public_aviation_compare_airports ~167

No description provided.

NameTypeReqDescription
airportsarrayyes–
response_formatstring––

No output schema declared.

No examples provided.

faa_public_aviation_search_airports ~290

No description provided.

NameTypeReqDescription
facility_typestring––
facility_usestring––
limitinteger––
min_runway_length_ftinteger––
offsetinteger––
querystring––
response_formatstring––
statestring––
statusstring––

No output schema declared.

No examples provided.

faa_public_aviation_search_runways ~338

No description provided.

NameTypeReqDescription
ils_onlyboolean––
lighted_onlyboolean––
limitinteger––
min_length_ftinteger––
min_width_ftinteger––
offsetinteger––
operational_onlyboolean––
public_use_onlyboolean––
response_formatstring––
statestring––
surfacestring––

No output schema declared.

No examples provided.

facility_care_quality ~373

No description provided.

NameTypeReqDescription
facilitystringyes–
statestring––
typestring––

No output schema declared.

No examples provided.

fbi_cde_compare_state_to_national ~252

No description provided.

NameTypeReqDescription
end_monthstringyes–
limitinteger––
offensestringyes–
offsetinteger––
response_formatstring––
start_monthstringyes–
statestringyes–

No output schema declared.

No examples provided.

fbi_cde_national_crime_trend ~215

No description provided.

NameTypeReqDescription
end_monthstringyes–
limitinteger––
offensestringyes–
offsetinteger––
response_formatstring––
start_monthstringyes–

No output schema declared.

No examples provided.

fbi_cde_state_crime_trend ~253

No description provided.

NameTypeReqDescription
end_monthstringyes–
limitinteger––
offensestringyes–
offsetinteger––
response_formatstring––
start_monthstringyes–
statestringyes–

No output schema declared.

No examples provided.

fbi_cde_state_month_snapshot ~173

No description provided.

NameTypeReqDescription
monthstringyes–
response_formatstring––
statestringyes–

No output schema declared.

No examples provided.

fbi_cde_state_reporting_coverage ~220

No description provided.

NameTypeReqDescription
end_monthstringyes–
limitinteger––
offsetinteger––
response_formatstring––
start_monthstringyes–
statestringyes–

No output schema declared.

No examples provided.

fbi_wanted ~90

No description provided.

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

fda_device_510k ~167

No description provided.

NameTypeReqDescription
end_datestring––
limitinteger––
product_codestring––
querystring––
start_datestring––

No output schema declared.

No examples provided.

fda_device_recalls ~141

No description provided.

NameTypeReqDescription
classificationstring––
end_datestring––
limitinteger––
querystring––
start_datestring––

No output schema declared.

No examples provided.

fda_drug_adverse_events ~201

No description provided.

NameTypeReqDescription
drugstringyes–
end_datestring––
limitinteger––
reactionstring––
serious_onlyboolean––
start_datestring––

No output schema declared.

No examples provided.

fda_drug_lookup ~122

No description provided.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

fda_drug_recalls ~159

No description provided.

NameTypeReqDescription
classificationstring––
end_datestring––
limitinteger––
querystring––
start_datestring––
statestring––

No output schema declared.

No examples provided.

fda_food_recalls ~143

No description provided.

NameTypeReqDescription
classificationstring––
end_datestring––
limitinteger––
querystring––
start_datestring––
statestring––

No output schema declared.

No examples provided.

fdic_deposits ~77

No description provided.

NameTypeReqDescription
citystring––
limitinteger––
statestring––

No output schema declared.

No examples provided.

fdic_failures ~122

No description provided.

NameTypeReqDescription
end_datestring––
limitinteger––
offsetinteger––
start_datestring––
statestring––

No output schema declared.

No examples provided.

Install

How do I install the LiveDataLink MCP server?

LiveDataLink is a hosted endpoint at https://livedatalink.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · livedatalink.ai

# add to Claude Code
claude mcp add --transport http blackboxfoundry-livedatalink 'https://livedatalink.ai/mcp'
Common questions

What is the LiveDataLink MCP server?

LiveDataLink is an MCP server listed in the public MCP registry as io.github.blackboxfoundry/livedatalink. 294 public-data tools across 60 domains; source freshness varies. Free tier. This page covers its hosted endpoint (https://livedatalink.ai/mcp).

Is the LiveDataLink MCP server safe to use?

LiveDataLink scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Does the LiveDataLink MCP server require authentication?

No. We connected to LiveDataLink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LiveDataLink MCP server still maintained?

LiveDataLink is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.