LiveDataLink
REMOTE · LIVEDATALINK.AI · SCANNED SEP 20
294 public-data tools across 60 domains; source freshness varies. Free tier.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http blackboxfoundry-livedatalink 'https://livedatalink.ai/mcp'
{
"mcpServers": {
"blackboxfoundry-livedatalink": {
"url": "https://livedatalink.ai/mcp"
}
}
} {
"servers": {
"blackboxfoundry-livedatalink": {
"type": "http",
"url": "https://livedatalink.ai/mcp"
}
}
} [mcp_servers.blackboxfoundry-livedatalink] url = "https://livedatalink.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"blackboxfoundry-livedatalink": {
"type": "remote",
"url": "https://livedatalink.ai/mcp",
"enabled": true
}
}
} openclaw mcp add blackboxfoundry-livedatalink --url 'https://livedatalink.ai/mcp' --transport streamable-http
mcp_servers:
blackboxfoundry-livedatalink:
url: "https://livedatalink.ai/mcp" {
"McpServers": {
"blackboxfoundry-livedatalink": {
"Transport": "http",
"Url": "https://livedatalink.ai/mcp"
}
}
} assistant mcp add blackboxfoundry-livedatalink -t streamable-http -u 'https://livedatalink.ai/mcp'
{
"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.
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
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 |
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 →
cftc_cot_compare ~209
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| markets | array | yes | – |
| report_type | string | yes | – |
| response_format | string | – | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
cftc_cot_evidence_pack ~145
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
cftc_cot_history ~329
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| end_date | string | – | – |
| limit | number | – | – |
| market | string | yes | – |
| offset | number | – | – |
| report_type | string | yes | – |
| response_format | string | – | – |
| scope | string | – | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
cftc_cot_latest ~144
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
cftc_cot_search_markets ~226
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| query | string | – | – |
| report_type | string | – | – |
| response_format | string | – | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
chemical_hazards ~164
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
chemical_lookup ~144
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
clinical_site_selector ~372
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| condition | string | yes | – |
| specialty | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
cms_home_health_search ~93
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| name_contains | string | – | – |
| offset | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
cms_hospice_search ~91
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| name_contains | string | – | – |
| offset | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
cms_hospital_search ~128
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| limit | number | – | – |
| name_contains | string | – | – |
| offset | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
cms_nursing_home_search ~97
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| name_contains | string | – | – |
| offset | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
college_accreditation ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_id | string | yes | – |
No output schema declared.
No examples provided.
college_compare ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_ids | array | yes | – |
No output schema declared.
No examples provided.
college_demographics ~56
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_id | string | yes | – |
No output schema declared.
No examples provided.
college_metrics ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_id | string | yes | – |
No output schema declared.
No examples provided.
college_outcomes_by_program ~52
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_id | string | yes | – |
No output schema declared.
No examples provided.
college_search ~124
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| accreditor | string | – | – |
| control | string | – | – |
| limit | number | – | – |
| name | string | – | – |
| size | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
college_trends ~102
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_year | number | yes | – |
| metric | string | yes | – |
| start_year | number | yes | – |
| unit_id | string | yes | – |
No output schema declared.
No examples provided.
college_value_score ~273
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| college | string | yes | – |
| program | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
company_complaint_profile ~310
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| since | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
company_info ~117
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
company_trust_check ~300
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| state | string | – | – |
| ticker | string | – | – |
No output schema declared.
No examples provided.
congress_bill_actions ~114
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | number | yes | – |
| bill_type | string | yes | – |
| congress | number | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
congress_bill_cosponsors ~116
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | number | yes | – |
| bill_type | string | yes | – |
| congress | number | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
congress_bill_details ~132
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | number | yes | – |
| bill_type | string | yes | – |
| congress | number | yes | – |
No output schema declared.
No examples provided.
congress_house_votes ~67
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | number | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
congress_member_details ~64
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bioguide_id | string | yes | – |
No output schema declared.
No examples provided.
congress_recent_laws ~92
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | number | – | – |
| law_type | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
congress_search_bills ~160
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | number | – | – |
| limit | number | – | – |
| offset | number | – | – |
| query | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
congress_search_members ~110
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | number | – | – |
| current_member | boolean | – | – |
| district | number | – | – |
| limit | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
corporate_ownership_tree ~323
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| lei | string | – | – |
No output schema declared.
No examples provided.
cost_of_doing_business_index ~312
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| metro | string | – | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
counterparty_risk_score ~218
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
No output schema declared.
No examples provided.
court_case_search ~138
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | – |
| date_filed_after | string | – | – |
| date_filed_before | string | – | – |
| judge | string | – | – |
| limit | number | – | – |
| party | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
court_citation_resolver ~54
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | – |
No output schema declared.
No examples provided.
court_docket_lookup ~76
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | yes | – |
| docket_number | string | yes | – |
No output schema declared.
No examples provided.
court_judge_lookup ~49
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
court_opinion_search ~65
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | – |
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
court_oral_argument_search ~66
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | – |
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
court_recent_filings ~60
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | yes | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
cpsc_recall_search ~230
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| date_end | string | – | – |
| date_start | string | – | – |
| hazard | string | – | – |
| limit | number | – | – |
| manufacturer | string | – | – |
| product | string | – | – |
| recall_number | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
cpsc_recent_recalls ~107
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| lookback_days | number | – | – |
No output schema declared.
No examples provided.
crypto_compare ~125
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| coins | – | yes | – |
No output schema declared.
No examples provided.
crypto_info ~109
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | – |
No output schema declared.
No examples provided.
crypto_price ~203
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | – |
No output schema declared.
No examples provided.
crypto_trending ~85
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cve_lookup ~70
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | – |
No output schema declared.
No examples provided.
cve_recent ~105
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
| limit | number | – | – |
| severity | string | – | – |
| vendor | string | – | – |
No output schema declared.
No examples provided.
cve_search_by_keyword ~94
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| limit | number | – | – |
| pub_end_date | string | – | – |
| pub_start_date | string | – | – |
No output schema declared.
No examples provided.
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.