FDA import alert red lists
REMOTE · REFERENCESOURCE.ORG · SCANNED SEP 21
Is a foreign supplier on an FDA import alert red list, detained at the US border? 14,000+ listings.
Available components
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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1025 tokens (~170/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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
claude mcp add --transport http joelp22-maker-referencesource-import-alerts 'https://referencesource.org/mcp/import-alerts'
{
"mcpServers": {
"joelp22-maker-referencesource-import-alerts": {
"url": "https://referencesource.org/mcp/import-alerts"
}
}
} {
"servers": {
"joelp22-maker-referencesource-import-alerts": {
"type": "http",
"url": "https://referencesource.org/mcp/import-alerts"
}
}
} [mcp_servers.joelp22-maker-referencesource-import-alerts] url = "https://referencesource.org/mcp/import-alerts"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joelp22-maker-referencesource-import-alerts": {
"type": "remote",
"url": "https://referencesource.org/mcp/import-alerts",
"enabled": true
}
}
} openclaw mcp add joelp22-maker-referencesource-import-alerts --url 'https://referencesource.org/mcp/import-alerts' --transport streamable-http
mcp_servers:
joelp22-maker-referencesource-import-alerts:
url: "https://referencesource.org/mcp/import-alerts" {
"McpServers": {
"joelp22-maker-referencesource-import-alerts": {
"Transport": "http",
"Url": "https://referencesource.org/mcp/import-alerts"
}
}
} assistant mcp add joelp22-maker-referencesource-import-alerts -t streamable-http -u 'https://referencesource.org/mcp/import-alerts'
{
"mcpServers": {
"joelp22-maker-referencesource-import-alerts": {
"type": "http",
"url": "https://referencesource.org/mcp/import-alerts"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 71
First indexed and scored.
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 Sept 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 | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9f260b3a10521b060ef7a85ccbf0f716 |
| 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. | present | 26974 | 8 | Verified |
| referencesource.org. | 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://referencesource.org/mcp/import-alerts | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp/import-alerts | HTTPS enforced | 301 | https://referencesource.org/mcp/import-alerts |
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 →
get_listing Get one red-list entry in full ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | The listing's record id, e.g. "argentina-54-16-molecular-dynamics-sas". |
| Name | Type | Req | Description |
|---|---|---|---|
| listing | object | yes | – |
| register | object | – | – |
No examples provided.
list_alert_firms List the firms red-listed on one import alert ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country filter. |
| import_alert_number | string | yes | The alert number as FDA prints it, e.g. "16-120" or "66-57". |
| limit | integer | – | How many to return, 1–20. Default 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| firms | array | yes | – |
| firms_matched | integer | yes | – |
| firms_returned | integer | – | – |
| import_alert_number | string | yes | – |
| register | object | – | – |
No examples provided.
list_import_alerts List the import alerts this register covers ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | yes | – |
| alerts_total | integer | yes | – |
| coverage | string | yes | – |
| register | object | – | – |
No examples provided.
list_recent_listings List firms added to a red list since a date ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| import_alert_number | string | – | Optional: only this alert. |
| limit | integer | – | How many to return, 1–20. Default 20. |
| since | string | yes | ISO date, e.g. "2025-01-01". FDA prints MM/DD/YYYY; this filter compares an ISO form computed here from that string. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| listings | array | yes | – |
| listings_matched | integer | yes | – |
| listings_returned | integer | – | – |
| register | object | – | – |
| since | string | yes | – |
No examples provided.
resolve_firm Find a firm on an FDA import alert red list ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country filter, e.g. "CHINA", "Vietnam". FDA prints countries in capitals; matching is case-insensitive. |
| firm_name | string | yes | Firm name or part of one. Case-insensitive substring match. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| firm_name | string | yes | – |
| listings | array | yes | – |
| listings_matched | integer | yes | – |
| listings_returned | integer | – | – |
| register | object | – | – |
No examples provided.
verify_quote Check a claimed import-alert fact against the register ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_value | string | yes | The value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29". |
| field | string | – | Which field the claim is about, if you know it. Without it, every stored field of the record is checked. |
| record_id | string | yes | The listing's record id, from resolve_firm or list_alert_firms. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | – |
| claimed_value | string | yes | – |
| in_source_quote | boolean | – | – |
| match | object | – | – |
| quote_source | string | – | – |
| record | object | – | – |
| stored_values | object | – | – |
| verdict | string | yes | matches_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.
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 71 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 6 tools: resolve_firm, get_listing, list_import_alerts, list_alert_firms, list_recent_listings, verify_quote. Their descriptions and schemas cost roughly 810 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.