Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FDA import alert red lists

REMOTE · REFERENCESOURCE.ORG

Is a foreign supplier on an FDA import alert red list, detained at the US border? 14,000+ listings.

0 this week 85 Trust /100

Last scanned (15 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1190 tokens (~170/item across 7 items; 7 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
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 0
    • Schema quality: 1025 → 1190 ▼ functional
    • New tool “watch” functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Probed https://referencesource.org/mcp/import-alerts

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=referencesource.org CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 284c538e5c38c80d0eb8e23b1bba01ab
SANs: referencesource.org
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 referencesource.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
referencesource.org. No DS 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://referencesource.org/mcp/import-alerts Verified 200
http (plaintext) http://referencesource.org/mcp/import-alerts HTTPS enforced 301 https://referencesource.org/mcp/import-alerts
MCP tools · 7 exposed · ~975 tokens

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 →

Tool Tokens
get_listing ~120

Everything FDA prints for one red-list entry: the firm name and address, the import alert and its title, the product code and description, FDA's stated reason (the Notes block — the actual finding, e.g. "Decomposition" or a confirmed laboratory result), and the date published, with the FDA page and a verbatim quote. Record IDs come from resolve_firm or list_alert_firms.

NameTypeReqDescription
record_idstringyesThe listing's record id, e.g. "argentina-54-16-molecular-dynamics-sas".
NameTypeReqDescription
listingobjectyes–
registerobject––

No examples provided.

list_alert_firms ~134

Who is on this import alert? Returns the firms red-listed on one alert number (from list_import_alerts), newest listing first, optionally narrowed to a country — for example every Vietnamese firm on 16-120, or every firm on 66-57. Each with the FDA page and a verbatim quote.

NameTypeReqDescription
countrystring–Optional country filter.
import_alert_numberstringyesThe alert number as FDA prints it, e.g. "16-120" or "66-57".
limitinteger–How many to return, 1–20. Default 20.
NameTypeReqDescription
coveragestringyes–
firmsarrayyes–
firms_matchedintegeryes–
firms_returnedinteger––
import_alert_numberstringyes–
registerobject––

No examples provided.

list_import_alerts ~80

Which FDA import alerts are in here, and how many firms are on each? Returns the alert number, FDA's own title for it, the number of firms red-listed, how many countries they are in, and the newest listing date. Call this first to see what can be answered, and to get an alert number for list_alert_firms.

Input schema present but exposes no named parameters.

NameTypeReqDescription
alertsarrayyes–
alerts_totalintegeryes–
coveragestringyes–
registerobject––

No examples provided.

list_recent_listings ~152

Who has FDA red-listed recently? Returns the listings whose published date is on or after a date you give, newest first, optionally for one alert. Use this to watch a category — new detentions on the seafood alerts, say — rather than to look a firm up. The date FDA prints is when the FIRM was added to the alert.

NameTypeReqDescription
import_alert_numberstring–Optional: only this alert.
limitinteger–How many to return, 1–20. Default 20.
sincestringyesISO date, e.g. "2025-01-01". FDA prints MM/DD/YYYY; this filter compares an ISO form computed here from that string.
NameTypeReqDescription
coveragestringyes–
listingsarrayyes–
listings_matchedintegeryes–
listings_returnedinteger––
registerobject––
sincestringyes–

No examples provided.

resolve_firm ~158

Is this supplier red-listed by FDA? Search the import alert red lists by firm name or part of one (e.g. "Tonga Tiur", "Qingdao", "pharmacy"), optionally narrowed to a country. Returns each listing with the import alert number and name, the country, the date FDA published the listing, and the FDA page and verbatim quote it was read from. A firm can appear more than once — one record per alert it is listed on.

NameTypeReqDescription
countrystring–Optional 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.
NameTypeReqDescription
coveragestringyes–
firm_namestringyes–
listingsarrayyes–
listings_matchedintegeryes–
listings_returnedinteger––
registerobject––

No examples provided.

verify_quote ~166

Is this right? Check a claim about a red-list entry — the alert number a firm is on, its country, the date it was published, FDA's stated reason — against the register instead of trusting it. Says whether the claim matches a stored value, appears only in the verbatim FDA quote, or differs (and then what FDA's page says instead).

NameTypeReqDescription
claimed_valuestringyesThe value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29".
fieldstring–Which field the claim is about, if you know it. Without it, every stored field of the record is checked.
record_idstringyesThe listing's record id, from resolve_firm or list_alert_firms.
NameTypeReqDescription
attestationstringyes–
claimed_valuestringyes–
in_source_quoteboolean––
matchobject––
quote_sourcestring––
recordobject––
stored_valuesobject––
verdictstringyesmatches_record: the claim equals a stored value (match.match_type says how exactly). matches_quote: it appears in the verbatim source quote but is not a stored value. differs: the record was found an…

No examples provided.

watch ~165

Polling this register every morning to see whether a firm is still on a red list? Watch the listing instead. Give the record id and this hands back one URL that answers "has it changed" in a single conditional request: 304 if nothing we hold about that listing has moved, 200 with the change and FDA's own sentence if it has. Same feed as Atom for a feed reader. This register records a before and after for each change, so the feed can say what it used to say. We do not push and store nothing about you — the URL is derived from the record id, so this makes your poll cheap and definite rather than notifying you.

NameTypeReqDescription
record_idstringyesThe listing's record id, from resolve_firm or list_alert_firms.
NameTypeReqDescription
attestationstringyes–
currentobject–What the register holds for this record right now, with its citation.
how_to_pollobjectyes–
watchingobjectyes–

No examples provided.

Install

How do I install the FDA import alert red lists MCP server?

FDA import alert red lists is a hosted endpoint at https://referencesource.org/mcp/import-alerts, 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 · referencesource.org

# add to Claude Code
claude mcp add --transport http joelp22-maker-referencesource-import-alerts 'https://referencesource.org/mcp/import-alerts'
Common questions

What is the FDA import alert red lists MCP server?

FDA import alert red lists is an MCP server listed in the public MCP registry as io.github.joelp22-maker/referencesource-import-alerts. Is a foreign supplier on an FDA import alert red list, detained at the US border? 14,000+ listings. This page covers its hosted endpoint (https://referencesource.org/mcp/import-alerts).

Is the FDA import alert red lists MCP server safe to use?

FDA import alert red lists 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.

What tools does the FDA import alert red lists MCP server expose?

FDA import alert red lists exposes 7 tools: resolve_firm, get_listing, list_import_alerts, list_alert_firms, list_recent_listings, and 2 more. Their descriptions and schemas cost roughly 975 tokens of context every time the server is loaded.

Does the FDA import alert red lists MCP server require authentication?

No. We connected to FDA import alert red lists without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FDA import alert red lists MCP server still maintained?

FDA import alert red lists is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the FDA import alert red lists MCP server?

VerifyMCP ran 13 checks on FDA import alert red lists, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.