Health · Remote MCP server
Rattlewatch
Cited US recall lookup for AI agents: CPSC and FDA data, nothing invented.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.veritylabsai/rattlewatch- Version
- 0.2.1
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- veritylabsai (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/veritylabsai) · how
- Website
- github.com/veritylabsai/rattlewatch
- Repository
- github.com/veritylabsai/rattlewatch
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://rattlewatch.rattled.ca/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- rattlewatch 0.2.1 · protocol 2025-06-18
- Tools discovered
- 4:
search_recalls,get_requirement,list_changes,verify - Checked on
- 2026-10-05
How to connect Rattlewatch
Rattlewatch is a remote MCP server: there is nothing to install. Its endpoint is https://rattlewatch.rattled.ca/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from veritylabsai (GitHub)
| Server | Runs |
|---|---|
| VerityCited product-compliance ground truth for AI agents. Never generates; always cites. | Remote · HTTPLive check: ✓ handshake |
More health servers
| Server | Runs |
|---|---|
| PyEuropePMCSearch and analyse scientific literature across Europe PMC, PubMed, arXiv, and ClinicalTrials.gov. | Local · stdio |
| QSimHealthHealthcare staffing simulator - ED, walk-in clinic, and appointment office DES tools. | Remote · HTTPLive check: ✓ handshake |
| Quiet MendersPrivacy clinic + pay-per-call data APIs for AI agents via x402. Never pays or touches keys. | Remote · HTTPLive check: ✓ handshake |
| RarasDisease Twin - Brazil's rare-disease knowledge graph (10,468) over MCP. Source-grounded, PT-BR. | Remote · HTTPLive check: ✓ handshake |
| recalert.usSearch U.S. product recalls (CPSC, FDA, NHTSA, FSIS) by product, brand, model, or UPC code. | Remote · HTTPLive check: ✓ handshake |
| Recall RiskCheck a product's recall risk: score + active CPSC/FDA/NHTSA recalls for a product or brand. | Remote · HTTPLive check: ✓ handshake |
| RecallRadarSearch U.S. FDA, USDA FSIS, and CPSC recalls, fetch one, or diff since a date. API key or x402. | Remote · HTTPLive check: ✓ handshake |
| Redacta MCPPseudonymise and restore patient identifiers & PII in text - local, HIPAA Safe Harbor mode. | Local · stdio |