LiveDataLink
REMOTE · LIVEDATALINK.AI
294 public-data tools across 60 domains; source freshness varies. Free tier.
Available components
Last scanned (2 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
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 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
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
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 |
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 →
fdic_financials ~89
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cert | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
fdic_history ~61
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cert | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
fdic_search_institutions ~157
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| city | string | – | – |
| limit | integer | – | – |
| name | string | – | – |
| offset | integer | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
fdic_summary ~71
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
fec_candidate_details ~84
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | – |
No output schema declared.
No examples provided.
fec_candidate_financials ~123
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | – |
| cycle | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
fec_candidate_search ~189
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| cycle | integer | – | – |
| limit | integer | – | – |
| office | string | – | – |
| party | string | – | – |
| query | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
fec_committee_search ~171
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| committee_type | string | – | – |
| cycle | integer | – | – |
| limit | integer | – | – |
| query | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
fec_independent_expenditures ~157
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | – | – |
| committee_id | string | – | – |
| cycle | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
fed_board_h15_evidence_pack ~131
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fed_board_h15_rate_history ~211
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| response_format | string | – | – |
| series | string | yes | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
fed_board_h15_rate_spread ~259
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| response_format | string | – | – |
| series_a | string | yes | – |
| series_b | string | yes | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
fed_board_h15_search_series ~160
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fed_board_h15_yield_curve ~151
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fed_z1_catalog ~188
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fed_z1_change ~209
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_period | string | yes | – |
| response_format | string | – | – |
| series | string | yes | – |
| start_period | string | yes | – |
No output schema declared.
No examples provided.
fed_z1_series ~233
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_period | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| response_format | string | – | – |
| series | string | yes | – |
| start_period | string | – | – |
No output schema declared.
No examples provided.
fed_z1_snapshot ~143
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| series | array | yes | – |
No output schema declared.
No examples provided.
fema_nfhl_compare_inventory_items ~114
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dfirm_ids | array | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fema_nfhl_get_inventory_item ~128
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dfirm_id | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fema_nfhl_get_snapshot_metadata ~112
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
No output schema declared.
No examples provided.
fema_nfhl_search_inventory ~317
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction_kind | string | – | – |
| limit | integer | – | – |
| max_advertised_mb | number | – | – |
| min_advertised_mb | number | – | – |
| offset | integer | – | – |
| query | string | – | – |
| response_format | string | – | – |
| sort | string | – | – |
| state | string | – | – |
| updated_from | string | – | – |
| updated_through | string | – | – |
No output schema declared.
No examples provided.
fema_nfhl_summarize_state_inventory ~123
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
fhfa_hpi_compare ~215
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency | string | – | – |
| geography_level | string | – | – |
| hpi_flavor | string | – | – |
| index_basis | string | – | – |
| places | array | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
fhfa_hpi_series ~298
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_year | integer | – | – |
| frequency | string | – | – |
| geography_level | string | – | – |
| hpi_flavor | string | – | – |
| index_basis | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| place | string | yes | – |
| response_format | string | – | – |
| start_year | integer | – | – |
No output schema declared.
No examples provided.
fhfa_hpi_trend ~239
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency | string | – | – |
| geography_level | string | – | – |
| hpi_flavor | string | – | – |
| index_basis | string | – | – |
| place | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
flood_zone_lookup ~113
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | – |
| location | string | – | – |
| lon | number | – | – |
No output schema declared.
No examples provided.
fmcsa_carrier_authority ~139
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dot_number | integer | yes | – |
No output schema declared.
No examples provided.
fmcsa_carrier_compare ~136
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dot_numbers | – | yes | – |
No output schema declared.
No examples provided.
fmcsa_carrier_lookup ~174
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dot_number | integer | – | – |
| mc_number | integer | – | – |
No output schema declared.
No examples provided.
fmcsa_carrier_search ~123
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
fmcsa_safety_scores ~166
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dot_number | integer | yes | – |
No output schema declared.
No examples provided.
fred_category_series ~111
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
fred_compare ~127
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | – |
| limit | integer | – | – |
| series_ids | array | yes | – |
| start | string | – | – |
No output schema declared.
No examples provided.
fred_observations ~262
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation_method | string | – | – |
| end | string | – | – |
| frequency | string | – | – |
| limit | integer | – | – |
| series_id | string | yes | – |
| start | string | – | – |
| units | string | – | – |
No output schema declared.
No examples provided.
fred_quick_indicator ~219
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | – |
| indicator | string | yes | – |
| limit | integer | – | – |
| start | string | – | – |
No output schema declared.
No examples provided.
fred_releases ~111
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| release_id | integer | – | – |
| upcoming_dates | boolean | – | – |
No output schema declared.
No examples provided.
fred_search ~138
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| search_text | string | yes | – |
| search_type | string | – | – |
| tag_names | string | – | – |
No output schema declared.
No examples provided.
fred_series_info ~85
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| series_id | string | yes | – |
No output schema declared.
No examples provided.
geocode_address ~182
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| city | string | – | – |
| state | string | – | – |
| street | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
geocode_batch ~85
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | – |
No output schema declared.
No examples provided.
geocode_coordinates ~87
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
No output schema declared.
No examples provided.
github_repo ~79
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | – |
No output schema declared.
No examples provided.
govinfo_legislation_committee_path ~171
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
govinfo_legislation_evidence_pack ~233
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action_limit | integer | – | – |
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
govinfo_legislation_relationships ~214
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
govinfo_legislation_search ~309
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_type | string | – | – |
| enacted_only | boolean | – | – |
| limit | integer | – | – |
| multiple_text_versions_only | boolean | – | – |
| offset | integer | – | – |
| policy_area | string | – | – |
| query | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
govinfo_legislation_version_lineage ~182
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| response_format | string | – | – |
No output schema declared.
No examples provided.
grants_get_opportunity ~88
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunityId | string | yes | – |
No output schema declared.
No examples provided.
grants_search ~248
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | string | – | – |
| eligibilities | string | – | – |
| fundingCategories | string | – | – |
| fundingInstruments | string | – | – |
| keyword | string | – | – |
| oppStatuses | string | – | – |
| rows | integer | – | – |
No output schema declared.
No examples provided.
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'
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.