Search 2.2M+ indexed records and reach hundreds of millions more from authoritative sources. Every result includes source and freshness context.
Try a live query in the browser · Browse source coverage and freshness.
1,000 queries/month free · No credit card · For MCP clients that support bearer-token authentication
Government, market, and regulatory data from the sources listed for each tool, all available through one endpoint. If a source is missing, tell us what you need and we will assess it for a future addition.
These examples show the tools involved and the source behind each result.
fmcsa_carrier_search → fmcsa_safety_scores → fmcsa_carrier_authority. The tools provide matching carriers, BASIC safety percentiles, and authority and insurance status for the agent to compare.sanctions_screen_entity → sanctions_screen_address → sanctions_search_alias. Returns hit/no-hit with source list and entity ID.stock_quote → options_chain → stock_compare. Returns the latest available quotes, IV, and side-by-side fundamentals. Timing depends on the source.These workflow packs gather related records, then return source notes, missing fields, and questions for a reviewer to follow up on.
Resolve the legal entity, collect identity signals, screen sanctions, and produce a load-release and credit-review checklist for one or both counterparties.
shipper_receiver_counterparty_packAssemble canonical identifiers, ownership-chain screening, public-record standing, source gaps, and a reviewer checklist into a reusable case file.
kyb_aml_evidence_case_fileCompare origin and destination hazards, environmental context, disaster history, and operational follow-ups before a shipment moves.
lane_location_risk_packEach pack is an informational public-record summary with source coverage and verification notes. It is not a credit decision, legal opinion, insurance rating, or sanctions clearance.
Inspect the deployed catalog, check service health, and test a source that matters to your workflow before you rely on it.
The live MCP endpoint currently exposes 377 public-data tools across 81 domains.
Browse the catalog →Try the free evaluation tier first, then verify important records at the primary source before using them in a decision.
Many of these data domains are also available from specialist vendors. Their pricing, licensing, coverage, and contract terms vary, so the comparison below is a prompt to verify your current source mix, not a market-price benchmark or a guaranteed saving.
The comparison is about consolidation, not a guaranteed replacement or savings claim. Check each provider's current pricing, licensing, coverage, and service terms before deciding what to replace.
Due-diligence workflows often combine several sources and vendor accounts. LiveDataLink puts sanctions, SEC filings, federal courts, IRS nonprofits, federal awards, environmental compliance, carrier safety, and bank-failure data behind one bearer token. Your agent can run the checks it needs.
Give the tool a company name and it returns a 0-100 score with the supporting records listed. It checks sanctions (OFAC/UN/EU/BIS), SEC EDGAR, federal courts, EPA enforcement, and federal contracts in one result.
This combines five public-data checks into one explainable response. Treat the result as a review aid, not a final compliance or credit decision.
sanctions_screen_entity → edgar_company_lookup → edgar_company_factscourt_case_search → caselaw_search → spending_search_awardsepa_facility_search → fmcsa_carrier_searchnonprofit_search_name → entity_resolve → entity_dossier
/api/usage/export. Export the log as CSV or JSON for your own records.Alternatives: separate source-specific APIs can mean more integrations and credentials. LiveDataLink Pro is $49/month for up to 50,000 queries per month, with the catalog available through one endpoint. Compare coverage, licensing, and support terms for your use case.
Every plan uses one API key for the catalog. The monthly price and included query limit are shown up front, with no per-tool charges. Plans pause at the limit until renewal.
Start with 1,000 queries/month across all 377 tools. No credit card required.
Get a free API key →You can build these connections yourself. The ongoing work is usually the hard part.
Works with Claude Desktop, Cursor, Continue, Cline, Zed, and other clients that support remote Streamable HTTP MCP servers. The model comes from your client. It just needs to support this connection method.
Subscribe above, or grab a free-tier API key at /signup/free (1,000 queries/month, no card).
For Claude Desktop, Cursor, and most MCP clients, add this block to your mcpServers config:
{
"mcpServers": {
"livedatalink": {
"url": "https://livedatalink.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY",
"Accept": "application/json, text/event-stream"
}
}
}
}
Verify everything works before relying on it:
curl -X POST https://livedatalink.ai/mcp \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
You should get back the tool catalog as JSON-RPC. Your MCP client can then call the tools it supports based on the user's prompt.
LiveDataLink gives an agent a documented connection to public data, with source and freshness notes kept visible.
LiveDataLink is designed for agents that need public data with a clear source trail and a stable connection method.
The discovery tool search_available_datasets is free, does not use query credits, and records unmet requests as product feedback. Those requests help set the order for future additions.
Use any client that supports remote Streamable HTTP MCP. Your user owns the key, and the integration uses a standard connection rather than a proprietary SDK.
Memory snippets, SKILL.md templates, and Cursor rule blocks are at livedatalink.ai/tools. Plain-text summary lives at /llms.txt. Full machine-readable JSON-LD catalog is in this page's head.
Review the catalog, check source notes, and start with a small evaluation.
Clear limits, source notes, and practical answers.
search_available_datasets) logs the search text to drive our build roadmap. Don't put PII in discovery searches.search_available_datasets, source quality, and maintenance cost to choose additions. A missing source is not a promise that it will be added. Email support@livedatalink.ai if you want us to assess one.