MCP.Market

Rattlewatch MCP server

online · 100% uptime
by veritylabsai·io.github.veritylabsai/rattlewatch·v0.2.1

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

B84/100grade B
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Rattlewatch yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Rattlewatch tools (4)

write = sends, deletes, buys or posts
  • get_requirementFree

    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.

  • list_changesFree

    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.

  • search_recallsFree

    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.

  • verifyFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 654ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 41 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Rattlewatch compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
476 ms
faster than 31% of 30,031 servers

What its tools let an agent do: 4 read

Install Rattlewatch in Claude Code, Cursor or VS Code

claude mcp add --transport http rattlewatch https://rattlewatch.rattled.ca/mcp
Add to Cursor

What the publisher says

From the Rattlewatch repository's README, as published. We do not edit it. Read it on GitHub

US product recall lookup for AI agents — CPSC consumer products and FDA food, drug and device enforcement, with every result pinned to an official source.

The point is not that it searches; it is that it refuses to answer without a citation. Ask it something it has no record of and it says so, rather than inventing a plausible answer.

Live API: https://rattlewatch.rattled.ca MCP endpoint: https://rattlewatch.rattled.ca/mcp Interactive docs: https://rattlewatch.rattled.ca/docs

Machine-readable discovery, for agents rather than browsers:

One container serves both surfaces — the REST API and MCP over streamable HTTP at /mcp. That matters for registry discovery: directories introspect the image's default command, so it has to be a working MCP server.

curl "https://rattlewatch.rattled.ca/v1/recalls/search?q=Bistro%20Pro%20Electric%20Grill"

Rattlewatch answers the questions an agent cannot safely answer itself:

  • Is this product, brand, or model number subject to a recall?
  • Which agency published that recall, and where is the source?
  • What recalls or rule changes appeared since a given date?

Every answer carries an official source URL and a last-verified date. Rattlewatch never generates an answer — it returns records that exist in its store, or it says "no verified record". Absence is an honest negative, not a guess.

The trust guarantee

An answer without a citation does not ship.

ECHA, the European Commission, OEHHA).

  • Cited — every fact and recall is pinned to an official source (CPSC, EUR-Lex,

a change event, never an in-place edit.

  • Versioned — facts are append-only. A changed answer creates a new version and

verified_at tells you exactly when.

  • Current — the store is re-verified against its upstream sources on a schedule;

it returns found: false with an explicit reason. It will not invent one.

  • Non-generative — verify() returns only matching records. If nothing matches,

Tools (MCP)

Data coverage

openFDA enforcement reports for food, drug and device. Every record carries a resolvable source URL: the official CPSC page, or a per-record openFDA query.

  • Recalls — the full structured U.S. CPSC feed (consumer products) plus

total: CPSIA/Children's Product Certificate, CPSC eFiling, EU GPSR, CE marking, REACH SVHCs, RoHS, and California Prop 65 — each with a verbatim citation. This is a companion to the recall data, not a regulatory database.

  • Requirements — a small curated set of cited market-entry facts, seven in
python -m rattlewatch build --max-recalls 5000 --fda-limit 3000   # default in the image
python -m rattlewatch build --fda-limit 0                          # CPSC only (used by CI)

The engine is domain-agnostic: new markets (UK, CA, AU, JP, and beyond) and new rule sets are added as more cited facts and feeds are compiled, without code change.

Quick start

python -m venv .venv && .venv/Scripts/activate   # or: source .venv/bin/activate
pip install -r requirements.txt

# build the store (facts + CPSC recalls)
python -m rattlewatch build

# run as an MCP server over stdio (local agents)
python -m rattlewatch mcp

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-01downgradeA → Bscore 84

Rattlewatch: common questions

Is Rattlewatch MCP server safe?
Mostly: it is graded B (84/100). Read the Rattlewatch safety report
How do I install Rattlewatch?
It runs remotely at rattlewatch.rattled.ca. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Rattlewatch need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Rattlewatch maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.2.1.
Is Rattlewatch up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Rattlewatch compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.