mcp-registry/io.github.blackboxfoundry/livedatalink · v1.9.0
Also listed as github/blackboxfoundry/livedatalink
As of 2026-10-19 10:37 UTC, the Blackboxfoundry Livedatalink MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.
294 public-data tools across 60 domains; source freshness varies. Free tier.
Claude Code
claude mcp add --transport http blackboxfoundry-livedatalink-mcp-server https://livedatalink.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"blackboxfoundry-livedatalink-mcp-server": {
"type": "http",
"url": "https://livedatalink.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Loading this server's tool list costs an agent ~94,030 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
381 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
28 parameter(s) across 12 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Handshake + tools/list takes ~2,072 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 221 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink/fixes
{
"name": "carrier_monitor_recheck",
"description": "Recheck an existing carrier snapshot and identify meaningful changes since the previous check. Accepts a DOT/MC/name plus the prior result or snapshot as previous_snapshot, then compares authority, identity, insurance summary, BASIC alerts, crashes, out-of-service indicators, safety rating, and verdict. Returns unchanged/changed status, a severity, field-level changes, and the next reviewer action. Store the returned current_snapshot in your own system and call this on a schedule; LiveDataLink d",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"mc": {
"type": "integer",
"description": "MC/MX number without the prefix."
},
"dot": {
"type": "integer",
"description": "USDOT number (preferred)."
},
"name": {
"type": "string",
"description": "Carrier legal name when DOT/MC is unavailable."
},
"format": {
"enum": [
"markdown",
"json"
],
"type": "string",
"description": "Report format. Defaults to markdown."
},
"previous_snapshot": {
"description": "Prior carrier_vetting result or JSON snapshot returned by an earlier call.",
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Carrier Monitor Recheck",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.blackboxfoundry/livedatalink"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.blackboxfoundry/livedatalink"}) over MCP.
cftc_cot_history ~610 tokensnasa_firms_search_fires ~599 tokensfema_nfhl_search_inventory ~593 tokensfhfa_hpi_series ~567 tokensfaa_public_aviation_search_runways ~560 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1e9af637262eb5f9…, first seen 2026-10-17, included at leaf 2265 of 26,213. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable search servers · most reliable retrieval servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 10:37 UTC, the Blackboxfoundry Livedatalink MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.
Blackboxfoundry Livedatalink MCP server advertises 300+ tools, including affordable_housing_refinance_evidence_pack, air_quality, bank_health_report, bea_compare_states, bea_search_state_indicators.
Point your MCP client at this streamable-http endpoint: https://livedatalink.ai/mcp
Glimind scanned all 381 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.