RecallRadar
REMOTE · RECALLRADAR.WITHGLINT.APP · SCANNED OCT 3
Search U.S. FDA, USDA FSIS, and CPSC recalls, fetch one, or diff since a date. API key or x402.
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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1501 tokens (~65/item across 23 items; 4 tools + 19 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the RecallRadar MCP server?
RecallRadar is a hosted endpoint at https://recallradar.withglint.app/mcp, 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 · recallradar.withglint.app
claude mcp add --transport http app-withglint-recallradar-recallradar 'https://recallradar.withglint.app/mcp'
{
"mcpServers": {
"app-withglint-recallradar-recallradar": {
"url": "https://recallradar.withglint.app/mcp"
}
}
} {
"servers": {
"app-withglint-recallradar-recallradar": {
"type": "http",
"url": "https://recallradar.withglint.app/mcp"
}
}
} [mcp_servers.app-withglint-recallradar-recallradar] url = "https://recallradar.withglint.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-withglint-recallradar-recallradar": {
"type": "remote",
"url": "https://recallradar.withglint.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-withglint-recallradar-recallradar --url 'https://recallradar.withglint.app/mcp' --transport streamable-http
mcp_servers:
app-withglint-recallradar-recallradar:
url: "https://recallradar.withglint.app/mcp" {
"McpServers": {
"app-withglint-recallradar-recallradar": {
"Transport": "http",
"Url": "https://recallradar.withglint.app/mcp"
}
}
} assistant mcp add app-withglint-recallradar-recallradar -t streamable-http -u 'https://recallradar.withglint.app/mcp'
{
"mcpServers": {
"app-withglint-recallradar-recallradar": {
"type": "http",
"url": "https://recallradar.withglint.app/mcp"
}
}
} 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.
- 3 Oct 26 0
- New resource “RecallRadar daily brief for 2026-10-03” functional
- 2 Oct 26 +1
- Schema quality: excellent → good functional
- New resource “RecallRadar daily brief for 2026-10-02” functional
- 1 Oct 26 0
- Schema quality: good → excellent functional
- New resource “RecallRadar daily brief for 2026-10-01” functional
- 30 Sept 26 +1
- New resource “RecallRadar daily brief for 2026-09-30” functional
- 29 Sept 26 0
- New resource “RecallRadar daily brief for 2026-09-29” functional
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- New resource “RecallRadar daily brief for 2026-09-27” functional
- 26 Sept 26 +1
- New resource “RecallRadar daily brief for 2026-09-26” functional
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 3 Oct 2026 · Probed https://recallradar.withglint.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=withglint.app | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a8290a3a1ace513b0e2809ccbc1b717e |
| SANs: withglint.app, *.withglint.app | ||||||
| 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 recallradar.withglint.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| withglint.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recallradar.withglint.app/mcp | Verified | 200 | |
| http (plaintext) | http://recallradar.withglint.app/mcp | Inconclusive | 405 |
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 →
diff_since Recalls changed since a timestamp ~259
Recalls created or updated after a timestamp, oldest change first; each row has change = created | updated. Pass meta.until as the next since. Paid: send Authorization: Bearer rk_… or an x402 payment in params._meta["x402/payment"]. Fixed price per call (x402 exact). RecallRadar indexes public recall notices from the FDA, USDA FSIS, and CPSC. The official agency notice is the authoritative source. Always confirm details at the linked source before acting. source_url is authoritative.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Ongoing, or unknown for agencies without lifecycle status |
| agency | string | – | – |
| brands | array | – | Whole-word match on normalized brand, firm, or product text |
| classes | array | – | Rows without a class (CPSC) always match |
| company | string | – | Company slug or name (firm, else brand) |
| cursor | string | – | next_cursor from the previous call |
| limit | integer | – | Rows to return. Paid per row returned. |
| q | string | – | Free text over product, reason, firm |
| since | string | yes | ISO 8601 timestamp; returns rows created or updated after it |
| status | string | – | – |
No output schema declared.
No examples provided.
get_recall Get one recall ~116
One recall by id or slug, with the raw agency payload and status history. Paid: send Authorization: Bearer rk_… or an x402 payment in params._meta["x402/payment"]. Fixed price per call (x402 exact). RecallRadar indexes public recall notices from the FDA, USDA FSIS, and CPSC. The official agency notice is the authoritative source. Always confirm details at the linked source before acting. source_url is authoritative.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 32-hex recall id or page slug |
No output schema declared.
No examples provided.
list_agencies List indexed agencies ~56
Agencies RecallRadar indexes and their labels. Free. RecallRadar indexes public recall notices from the FDA, USDA FSIS, and CPSC. The official agency notice is the authoritative source. Always confirm details at the linked source before acting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_recalls Search US product recalls ~265
Search FDA, USDA FSIS, and CPSC recalls by brand, company, free text, agency, class, status, and published date, newest first. Paid: send Authorization: Bearer rk_… or an x402 payment in params._meta["x402/payment"]. Priced per row returned (x402 upto). RecallRadar indexes public recall notices from the FDA, USDA FSIS, and CPSC. The official agency notice is the authoritative source. Always confirm details at the linked source before acting. source_url is authoritative.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Ongoing, or unknown for agencies without lifecycle status |
| agency | string | – | – |
| brands | array | – | Whole-word match on normalized brand, firm, or product text |
| classes | array | – | Rows without a class (CPSC) always match |
| company | string | – | Company slug or name (firm, else brand) |
| cursor | string | – | next_cursor from the previous call |
| limit | integer | – | Rows to return. Paid per row returned. |
| q | string | – | Free text over product, reason, firm |
| since | string | – | published_at >= since |
| status | string | – | – |
| until | string | – | published_at <= until |
No output schema declared.
No examples provided.
What is the RecallRadar MCP server?
RecallRadar is an MCP server listed in the public MCP registry as app.withglint.recallradar/recallradar. Search U.S. FDA, USDA FSIS, and CPSC recalls, fetch one, or diff since a date. API key or x402. This page covers its hosted endpoint (https://recallradar.withglint.app/mcp).
Is the RecallRadar MCP server safe to use?
RecallRadar scores 79 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 RecallRadar MCP server expose?
RecallRadar exposes 4 tools: diff_since, get_recall, list_agencies, search_recalls. Their descriptions and schemas cost roughly 696 tokens of context every time the server is loaded.
Does the RecallRadar MCP server require authentication?
No. We connected to RecallRadar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RecallRadar MCP server still maintained?
RecallRadar is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.