# us.recalert/mcp (remote · ajlswjtsikbnpicienyu.supabase.co)

Search U.S. product recalls (CPSC, FDA, NHTSA, FSIS) by product, brand, model, or UPC code.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `ajlswjtsikbnpicienyu.supabase.co`: 70/100 (this document), [markdown](https://verifymcp.io/servers/us-recalert-mcp/functions-v1-mcp.md), [page](https://verifymcp.io/servers/us-recalert-mcp/functions-v1-mcp)

## Channel facts

- Endpoint: `https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 387 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http us-recalert-mcp 'https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "us-recalert-mcp": {
      "url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "us-recalert-mcp": {
      "type": "http",
      "url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.us-recalert-mcp]
url = "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-recalert-mcp": {
      "type": "remote",
      "url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add us-recalert-mcp --url 'https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  us-recalert-mcp:
    url: "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "us-recalert-mcp": {
      "Transport": "http",
      "Url": "https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add us-recalert-mcp -t streamable-http -u 'https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 69, +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.

### 2026-09-25 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 68, +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.

### 2026-09-21 (score 67, +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.

### 2026-09-19 (score 66, +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.

### 2026-09-17 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 64)

First indexed and scored.

## MCP tools (5)

### `search_recalls` (~103 tokens)

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.

Input parameters:

- `fuente` (string): Optional: restrict to one agency.
- `limit` (integer)
- `query` (string): Free-text search: product name, brand, or model.

### `list_agencies` (~44 tokens)

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.

### `check_upcs` (~95 tokens)

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).

Input parameters:

- `api_key` (string, required): Your Recalert API key.
- `upcs` (array, required): List of UPC codes to check.

### `get_recall_detail` (~97 tokens)

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).

Input parameters:

- `api_key` (string, required): Your Recalert API key.
- `fuente` (string, required)
- `numero_oficial` (string, required): The agency's official recall/case number.

### `get_pricing` (~48 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/us-recalert-mcp/functions-v1-mcp#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 69
- 2026-09-26: 69
- 2026-09-25: 68
- 2026-09-24: 68
- 2026-09-23: 68
- 2026-09-22: 67
- 2026-09-21: 67
- 2026-09-20: 66
- 2026-09-19: 66
- 2026-09-18: 65
- 2026-09-17: 65
- 2026-09-16: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://ajlswjtsikbnpicienyu.supabase.co/functions/v1/mcp
- Website: https://recalert.us/
- Changelog RSS feed: https://verifymcp.io/servers/us-recalert-mcp/functions-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/us-recalert-mcp/functions-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/us-recalert-mcp/functions-v1-mcp