Verity

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.

• Cited — every fact and recall is pinned to an official source (CPSC, EUR-Lex, ECHA, the European Commission, OEHHA).
• Versioned — facts are append-only. A changed answer creates a new version and a change event, never an in-place edit.
• Current — the store is re-verified against its upstream sources on a schedule; verified_at tells you exactly when.
• Non-generative — verify() returns only matching records. If nothing matches, it returns found: false with an explicit reason. It will not invent one.

---

Tools (MCP)

Data coverage

• Recalls — the full structured U.S. CPSC feed (consumer products) plus 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.
• Requirements — a small curated set of cited market-entry facts, seven in 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.

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

or serve the REST API + MCP over HTTP

python -m rattlewatch serve --host 0.0.0.0 --port 8000

Connect a client

{

"mcpServers": { "rattlewatch": { "command": "python", "args": ["-m", "rattlewatch", "mcp"], "cwd": "/path/to/rattlewatch" } } }

---

REST API

Interactive docs: /docs.

Pricing

Free discovery and lookups, metered premium calls. The premium endpoint implements the x402 payment flow: the server returns 402 Payment Required with a structured payment requirement, and a paying agent retries with proof of payment. This is the monetization thesis in one endpoint — *agents discover, agents pay*. The payment rail (x402/USDC or Stripe metered billing) is wired at deploy time.

---

Repository

rattlewatch/

rattlewatch/ store.py # ground-truth store (facts, recalls, events, sources) compile.py # ingest CPSC + cited rules engine.py # query logic (search, verify, change feed) textutil.py # normalization + matching primitives mcp_server.py # MCP server (stdio + streamable HTTP) api.py # FastAPI REST + x402 stub main.py # CLI: build / stats / serve / mcp data/rules/seed.yaml # cited facts tests/test_engine.py # correctness + no-hallucination tests

Why this matters

AI generates infinite plausible text for free, so content is worth nothing. But AI hallucinates — especially on current rules, specific numbers, and what changed last week. Rattlewatch is the opposite of a generative model: a small, boring, cited layer of truth that agents and the software they power can depend on when being wrong is expensive.

Security

See [SECURITY.md](SECURITY.md) for the full threat model, the implemented controls, and — listed explicitly — what is not protected. Every claim there is backed by a test in tests/test_api.py.

Highlights: query input bounded at two independent layers; per-client rate limiting; API keys compared in constant time that fail closed; CORS denied by default; hardened response headers; no stack-trace leakage; container runs as an unprivileged user (UID 10001).

Testing

export PYTHONPATH=.

python tests/test_engine.py # 13 checks — correctness + non-hallucination python tests/test_api.py # 30 checks — security + abuse

See [TESTING.md](TESTING.md) for the coverage map and an explicit list of what is *not* tested. A green run is not the same as "verified secure."

License

MIT — see LICENSE.

The code is open source; the hosted service is the product. Nothing about the moat lives in the source: the defensible asset is the curated, daily-refreshed, cited corpus and the freshness pipeline that maintains it. Open-sourcing the code also means the citation machinery is auditable — which matters for a product whose entire claim is that its answers can be trusted.

You can self-host it:

docker build -t rattlewatch .

docker run -p 8000:8000 rattlewatch

Or use the hosted endpoint: https://rattlewatch.rattled.ca