# Rattlewatch (remote · rattlewatch.rattled.ca)

Cited US recall lookup for AI agents: CPSC and FDA data, nothing invented.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `rattlewatch.rattled.ca`: 73/100 (this document), [markdown](https://verifymcp.io/servers/veritylabsai-rattlewatch/rattlewatch.md), [page](https://verifymcp.io/servers/veritylabsai-rattlewatch/rattlewatch)

## Channel facts

- Endpoint: `https://rattlewatch.rattled.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 332 tokens (~83/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Rattlewatch MCP server?

Rattlewatch is a hosted endpoint at https://rattlewatch.rattled.ca/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 veritylabsai-rattlewatch 'https://rattlewatch.rattled.ca/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "veritylabsai-rattlewatch": {
      "url": "https://rattlewatch.rattled.ca/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "veritylabsai-rattlewatch": {
      "type": "http",
      "url": "https://rattlewatch.rattled.ca/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.veritylabsai-rattlewatch]
url = "https://rattlewatch.rattled.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "veritylabsai-rattlewatch": {
      "type": "remote",
      "url": "https://rattlewatch.rattled.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add veritylabsai-rattlewatch --url 'https://rattlewatch.rattled.ca/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  veritylabsai-rattlewatch:
    url: "https://rattlewatch.rattled.ca/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "veritylabsai-rattlewatch": {
      "Transport": "http",
      "Url": "https://rattlewatch.rattled.ca/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add veritylabsai-rattlewatch -t streamable-http -u 'https://rattlewatch.rattled.ca/mcp'
```

### Other

```json
{
  "mcpServers": {
    "veritylabsai-rattlewatch": {
      "type": "http",
      "url": "https://rattlewatch.rattled.ca/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-27 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 72, +1)

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

### 2026-09-23 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 70)

First indexed and scored.

## MCP tools (4)

### `search_recalls` (~90 tokens)

Search official US recall records by product name, brand, model, or UPC. Covers CPSC consumer products and FDA food, drug and device enforcement. Returns only cited records from the store, each with a source URL and a match score. If nothing matches, returns an empty list rather than guessing.

Input parameters:

- `limit` (integer)
- `market` (string)
- `query` (string, required)

### `get_requirement` (~102 tokens)

Get cited market-entry requirements for a product subject in a given market (e.g. subject='childrens_products', market='US'). This is a small curated set, not a full regulatory database: CPC, CPSC eFiling, EU GPSR, CE marking, REACH SVHC, RoHS and California Prop 65. Returns each fact with its official citation URL and last-verified date.

Input parameters:

- `market`
- `subject` (string, required)

### `list_changes` (~70 tokens)

List recall and requirement changes since an ISO-8601 timestamp (e.g. '2026-09-01T00:00:00+00:00'). Includes newly published recalls and rule changes, each with its source URL.

Input parameters:

- `limit` (integer)
- `since` (string, required)

### `verify` (~70 tokens)

Check a claim or product query against the store. Returns only cited records (recalls and requirements) that match. Explicitly reports 'no verified record' when nothing matches -- it never synthesizes an answer, so absence means 'not in the store', not a negative claim.

Input parameters:

- `query` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/veritylabsai-rattlewatch/rattlewatch#diagnostics

## Score history

- 2026-09-27: 73
- 2026-09-26: 72
- 2026-09-25: 72
- 2026-09-24: 71
- 2026-09-23: 71
- 2026-09-22: 70
- 2026-09-21: 70

## Common questions

### What is the Rattlewatch MCP server?

Rattlewatch is an MCP server listed in the public MCP registry as io.github.veritylabsai/rattlewatch. Cited US recall lookup for AI agents: CPSC and FDA data, nothing invented. This page covers its hosted endpoint (https://rattlewatch.rattled.ca/mcp).

### Is the Rattlewatch MCP server safe to use?

Rattlewatch scores 73 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 Rattlewatch MCP server expose?

Rattlewatch exposes 4 tools: search_recalls, get_requirement, list_changes, verify. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.

### Does the Rattlewatch MCP server require authentication?

No. We connected to Rattlewatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rattlewatch MCP server still maintained?

Rattlewatch is still listed as active in the MCP registry. We last reached this channel on 27 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://rattlewatch.rattled.ca/mcp
- Repository: https://github.com/veritylabsai/rattlewatch
- Changelog RSS feed: https://verifymcp.io/servers/veritylabsai-rattlewatch/rattlewatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/veritylabsai-rattlewatch/rattlewatch.json
- HTML version of this page: https://verifymcp.io/servers/veritylabsai-rattlewatch/rattlewatch