us.recalert/mcp
REMOTE · AJLSWJTSIKBNPICIENYU.SUPABASE.CO · SCANNED SEP 28
Search U.S. product recalls (CPSC, FDA, NHTSA, FSIS) by product, brand, model, or UPC code.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 387 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the us.recalert/mcp server?
us.recalert/mcp is a hosted endpoint at https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/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 · ajlswjtsikbnpicienyu.supabase.co
claude mcp add --transport http us-recalert-mcp 'https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp'
{
"mcpServers": {
"us-recalert-mcp": {
"url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
}
}
} {
"servers": {
"us-recalert-mcp": {
"type": "http",
"url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
}
}
} [mcp_servers.us-recalert-mcp] url = "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-recalert-mcp": {
"type": "remote",
"url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp",
"enabled": true
}
}
} openclaw mcp add us-recalert-mcp --url 'https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp' --transport streamable-http
mcp_servers:
us-recalert-mcp:
url: "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp" {
"McpServers": {
"us-recalert-mcp": {
"Transport": "http",
"Url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
}
}
} assistant mcp add us-recalert-mcp -t streamable-http -u 'https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp'
{
"mcpServers": {
"us-recalert-mcp": {
"type": "http",
"url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 64
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 28 Sept 2026 · Probed https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 ajlswjtsikbnpicienyu.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | 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=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp | Verified | 200 | |
| http (plaintext) | http://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp | HTTPS enforced | 301 | https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp |
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 →
check_upcs ~95
Paid — the main action. Cross-checks up to 500 UPCs against Recalert's unified recall database in one call. Requires api_key (get one free at https://recalert.us/en/data). Costs 10 credits per UPC checked ($0.01/UPC).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Recalert API key. |
| upcs | array | yes | List of UPC codes to check. |
No output schema declared.
No examples provided.
get_pricing ~48
Free. Returns Recalert's pricing: human subscription tiers (Starter/Pro/Business) and the agent/API credit packages and per-call costs for this MCP server. No api_key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recall_detail ~97
Paid. Returns the full unified-schema record for one specific recall (fuente + numero_oficial): hazard, remedy, manufacturer, distributor, official URL, and versioned metadata. Requires api_key. Costs 2 credits ($0.002).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Recalert API key. |
| fuente | string | yes | – |
| numero_oficial | string | yes | The agency's official recall/case number. |
No output schema declared.
No examples provided.
list_agencies ~44
Free. Lists the four U.S. federal agencies Recalert covers, with how many recalls are indexed from each and when each was last updated. No api_key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_recalls ~103
Free. Search U.S. product recalls from CPSC, FDA, NHTSA and FSIS by keyword, brand, model or source. No api_key required. This is the free hook — use get_recall_detail or check_upcs for the unified/paid data.
| Name | Type | Req | Description |
|---|---|---|---|
| fuente | string | – | Optional: restrict to one agency. |
| limit | integer | – | – |
| query | string | – | Free-text search: product name, brand, or model. |
No output schema declared.
No examples provided.
What is the us.recalert/mcp server?
us.recalert/mcp is listed in the public MCP registry as us.recalert/mcp. Search U.S. product recalls (CPSC, FDA, NHTSA, FSIS) by product, brand, model, or UPC code. This page covers its hosted endpoint (https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp).
Is the us.recalert/mcp server safe to use?
us.recalert/mcp scores 70 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 us.recalert/mcp server expose?
us.recalert/mcp exposes 5 tools: search_recalls, list_agencies, check_upcs, get_recall_detail, get_pricing. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.
Does the us.recalert/mcp server require authentication?
No. We connected to us.recalert/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the us.recalert/mcp server still maintained?
us.recalert/mcp is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.