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 · SCANNED SEP 20

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

Available components

0 this week 85 Trust /100
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 Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 57254 tokens (~151/item across 377 items; 377 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: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 94 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
  • 99% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 377 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 378 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "blackboxfoundry-livedatalink": {
      "url": "https://livedatalink.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "blackboxfoundry-livedatalink": {
      "type": "http",
      "url": "https://livedatalink.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.blackboxfoundry-livedatalink]
url = "https://livedatalink.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "blackboxfoundry-livedatalink": {
      "type": "remote",
      "url": "https://livedatalink.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add blackboxfoundry-livedatalink --url 'https://livedatalink.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  blackboxfoundry-livedatalink:
    url: "https://livedatalink.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "blackboxfoundry-livedatalink": {
      "Transport": "http",
      "Url": "https://livedatalink.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add blackboxfoundry-livedatalink -t streamable-http -u 'https://livedatalink.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "blackboxfoundry-livedatalink": {
      "type": "http",
      "url": "https://livedatalink.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 20 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 13 Sept 26 0
    • Schema quality: 51840 → 57254 functional
    • 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 20 Sept 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 3799 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 · 377 exposed · ~57,098 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
gsa_per_diem_mie_breakdown ~93

No description provided.

NameTypeReqDescription
fiscal_yearnumberyes

No output schema declared.

No examples provided.

hurricane_tracker ~66

No description provided.

NameTypeReqDescription
basinstring

No output schema declared.

No examples provided.

influence_network_map ~281

No description provided.

NameTypeReqDescription
companystring
organizationstringyes
statestring
yearstring

No output schema declared.

No examples provided.

ip_reputation ~85

No description provided.

NameTypeReqDescription
ipstringyes

No output schema declared.

No examples provided.

issuer_diligence_dossier ~249

No description provided.

NameTypeReqDescription
companystringyes
statestring
tickerstring

No output schema declared.

No examples provided.

iv_analytics ~180

No description provided.

NameTypeReqDescription
as_ofstring
lookback_daysnumber
tickerstringyes

No output schema declared.

No examples provided.

kev_status_check ~53

No description provided.

NameTypeReqDescription
cve_idstringyes

No output schema declared.

No examples provided.

kyb_aml_evidence_case_file ~159

No description provided.

NameTypeReqDescription
companystringyes
einstring
formatstring
leistring
statestring
tickerstring

No output schema declared.

No examples provided.

lane_location_risk_pack ~179

No description provided.

NameTypeReqDescription
destination_addressstringyes
destination_areastring
destination_statestring
formatstring
origin_addressstringyes
origin_areastring
origin_statestring

No output schema declared.

No examples provided.

lei_hierarchy ~198

No description provided.

NameTypeReqDescription
children_limitnumber
querystringyes

No output schema declared.

No examples provided.

lei_lookup ~250

No description provided.

NameTypeReqDescription
limitnumber
querystringyes

No output schema declared.

No examples provided.

leie_exclusion_details ~64

No description provided.

NameTypeReqDescription
exclusion_idstringyes

No output schema declared.

No examples provided.

leie_lookup_npi ~92

No description provided.

NameTypeReqDescription
npistringyes

No output schema declared.

No examples provided.

leie_search_exclusions ~101

No description provided.

NameTypeReqDescription
limitnumber
namestringyes
statestring

No output schema declared.

No examples provided.

list_tool_groups ~128

No description provided.

NameTypeReqDescription
querystring

No output schema declared.

No examples provided.

load_tender_fraud_shield ~225

No description provided.

NameTypeReqDescription
carrier_addressstring
dotnumber
formatstring
load_idstring
mcnumber
namestring

No output schema declared.

No examples provided.

lobbying_contributions ~103

No description provided.

NameTypeReqDescription
filing_yearnumber
lobbyist_namestring
page_sizenumber
registrant_namestring

No output schema declared.

No examples provided.

lobbying_detail ~56

No description provided.

NameTypeReqDescription
filing_uuidstringyes

No output schema declared.

No examples provided.

lobbying_lobbyists ~95

No description provided.

NameTypeReqDescription
lobbyist_namestring
pagenumber
page_sizenumber
registrant_namestring

No output schema declared.

No examples provided.

lobbying_registrants ~60

No description provided.

NameTypeReqDescription
page_sizenumber
registrant_namestring

No output schema declared.

No examples provided.

lobbying_search ~231

No description provided.

NameTypeReqDescription
client_namestring
filing_typestring
filing_yearnumber
issue_codestring
pagenumber
page_sizenumber
registrant_namestring

No output schema declared.

No examples provided.

local_search ~202

No description provided.

NameTypeReqDescription
locationstringyes
querystringyes
radiusnumber

No output schema declared.

No examples provided.

location_risk_report ~215

No description provided.

NameTypeReqDescription
addressstring
latnumber
lonnumber
statestring

No output schema declared.

No examples provided.

market_size_estimator ~358

No description provided.

NameTypeReqDescription
industrystring
metrostring
naicsstring
statestring

No output schema declared.

No examples provided.

nasa_firms_search_fires ~335

No description provided.

NameTypeReqDescription
data_modestring
day_rangenumber
eastnumberyes
limitnumber
northnumberyes
offsetnumber
response_formatstring
sourcestring
southnumberyes
start_datestring
westnumberyes

No output schema declared.

No examples provided.

nfip_flood_claims ~136

No description provided.

NameTypeReqDescription
countystring
end_yearnumber
limitnumber
start_yearnumber
statestring
zipstring

No output schema declared.

No examples provided.

nonprofit_details ~105

No description provided.

NameTypeReqDescription
einstringyes

No output schema declared.

No examples provided.

nonprofit_lookup_ein ~100

No description provided.

NameTypeReqDescription
einstringyes

No output schema declared.

No examples provided.

nonprofit_search_location ~124

No description provided.

NameTypeReqDescription
citystring
limitnumber
statestring
zipstring

No output schema declared.

No examples provided.

nonprofit_search_name ~129

No description provided.

NameTypeReqDescription
limitnumber
namestringyes
statestring

No output schema declared.

No examples provided.

nonprofit_status ~105

No description provided.

NameTypeReqDescription
einstringyes

No output schema declared.

No examples provided.

npi_lookup ~65

No description provided.

NameTypeReqDescription
npistringyes

No output schema declared.

No examples provided.

npi_search_organization ~96

No description provided.

NameTypeReqDescription
citystring
limitnumber
organization_namestringyes
statestring

No output schema declared.

No examples provided.

npi_search_provider ~114

No description provided.

NameTypeReqDescription
citystring
first_namestring
last_namestringyes
limitnumber
statestring

No output schema declared.

No examples provided.

npi_search_specialty ~115

No description provided.

NameTypeReqDescription
citystring
limitnumber
statestring
taxonomystringyes

No output schema declared.

No examples provided.

npm_package ~78

No description provided.

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

nport_compare_funds ~124

No description provided.

NameTypeReqDescription
fund_astringyes
fund_bstringyes
limitnumber

No output schema declared.

No examples provided.

nport_fund_holdings ~115

No description provided.

NameTypeReqDescription
fundstringyes
limitnumber

No output schema declared.

No examples provided.

nrel_alt_fuel_station_detail ~55

No description provided.

NameTypeReqDescription
station_idnumberyes

No output schema declared.

No examples provided.

nrel_alt_fuel_stations ~220

No description provided.

NameTypeReqDescription
fuel_typestring
latnumber
limitnumber
locationstring
lonnumber
radiusnumber
statestring
statusstring

No output schema declared.

No examples provided.

nrel_pvwatts ~282

No description provided.

NameTypeReqDescription
addressstring
array_typenumber
azimuthnumber
latnumber
lonnumber
lossesnumber
module_typenumber
system_capacitynumberyes
tiltnumber

No output schema declared.

No examples provided.

nrel_solar_resource ~113

No description provided.

NameTypeReqDescription
addressstring
latnumber
lonnumber

No output schema declared.

No examples provided.

nrel_utility_rates ~113

No description provided.

NameTypeReqDescription
addressstring
latnumber
lonnumber

No output schema declared.

No examples provided.

nws_active_alerts ~115

No description provided.

NameTypeReqDescription
latnumber
locationstring
lonnumber
statestring
zonestring

No output schema declared.

No examples provided.

ok_wells_search ~295

No description provided.

NameTypeReqDescription
apistring
countystring
limitnumber
operatorstring
well_typestring

No output schema declared.

No examples provided.

open_payments_by_company ~66

No description provided.

NameTypeReqDescription
limitnumber

No output schema declared.

No examples provided.

open_payments_by_specialty ~53

No description provided.

NameTypeReqDescription
limitnumber

No output schema declared.

No examples provided.

open_payments_national_summary ~42

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_payments_ownership ~171

No description provided.

NameTypeReqDescription
companystring
doctorstring
limitnumber
specialtystring
statestring
yearstring

No output schema declared.

No examples provided.

open_payments_research ~165

No description provided.

NameTypeReqDescription
companystring
doctorstring
limitnumber
specialtystring
statestring
yearstring

No output schema declared.

No examples provided.

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 85 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.