mcpField
F
FDA import alert red lists

FDA import alert red lists

Remote
referencesource.orgLegal & Government0Updated 5w ago

About FDA import alert red lists

The FDA import alert red lists dataset on referencesource.org is searchable through its MCP server. It helps importers and compliance teams check published listings, with source URLs and verbatim quotes for tracing each record.

Key features

  1. 01Search FDA import alert listings
  2. 02Return source URLs and exact quotes
  3. 03Retrieve records with provenance
  4. 04Check claims against published records

Use cases

  1. 01Check a foreign supplier's listing
  2. 02Review a listing during import screening
  3. 03Trace a result to its source

MCP support

The referencesource.org MCP server exposes dataset search, record retrieval, and claim verification tools. Clients can access it through referencesource-mcp or the streamable-HTTP endpoint.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://referencesource.org/mcp/import-alerts
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

6
ParameterTypeRequiredDescription
countrystringNoOptional country filter, e.g. "CHINA", "Vietnam". FDA prints countries in capitals; matching is case-insensitive.
firm_namestringYesFirm name or part of one. Case-insensitive substring match.

Details

From the project README

referencesource-mcp

referencesource.org MCP connector

MCP server for referencesource.org — small, verified reference datasets where every record carries its source URL and a verbatim quote from that page, so any value an assistant gives you can be checked, not just believed.

285 datasets, 110,000+ records: regulatory thresholds and deadlines, version compatibility, standards supersessions, certification registers, inspection requirements, and more. Each dataset states its coverage and its last-verified date.

Tools

toolwhat it does
list_datasetsevery dataset with record counts and descriptions
search_recordssearch within a dataset; each hit returns the value plus its source URL and verbatim source quote
get_recordone record by id, full provenance included
verify_quotegive it a dataset slug and a value you already hold (record id and field optional) — it checks that claim against our published records and says whether it matches

verify_quote is the unusual one: assistants invent plausible-but-wrong values roughly 19% of the time in our own measurements, and this is the check. Four verdicts come back:

verdictwhat it means
matches_recordthe claim equals the stored value; the match type is named (exact, case-insensitive, normalised)
matches_quotenot a stored value, but it does appear in the record's source quote
differsthe record holds a different value — both are returned, with the source
not_foundno record in that dataset carries it

Where a record is found, the answer carries the stored value, the record URL, the source URL and the verbatim quote, so the claim can be traced upstream — plus an attestation saying plainly that the verdict is about what our source states, not about what is true in the world. Asking whether the 2026 conforming loan limit for Autauga County, Alabama is $806,500 returns differs, stored value $832,750, quoting the FHFA row it came from.

Scope, stated so nobody overclaims: these tools search referencesource.org's own published records. They do not fetch arbitrary URLs and cannot check a claim against a page we have not harvested. not_found means "not in this dataset", never "false".

Setup

Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "referencesource": {
      "command": "npx",
      "args": ["-y", "referencesource-mcp"]
    }
  }
}

Cursor / other stdio MCP clients — same idea: command npx, args ["-y", "referencesource-mcp"].

Clients that support remote servers directly don't need this package at all — point them at the streamable-HTTP endpoint: https://referencesource.org/mcp.

Notes

  • Zero dependencies; Node 18+. The package is a thin stdio→HTTPS bridge to the stateless server at referencesource.org/mcp.
  • No accounts, no keys, no tracking beyond standard server request logs (see referencesource.org/privacy).
  • Data is free to read on the site in HTML, Markdown, and JSON; this package just makes it callable mid-conversation.

MIT licensed.

The data behind it

Every record carries source (the page the value was read from) and source_quote (the verbatim line on that page which states it), so any answer this server returns can be checked against its source. verify_quote runs that check against a value you already hold: it tells you whether our record agrees, and hands back the source and quote either way.

Licence

MIT — see LICENSE. The reference data itself is CC BY 4.0; see the data repository for the full position on the quoted excerpts.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.