Rattlewatch
REMOTE · RATTLEWATCH.RATTLED.CA · SCANNED SEP 27
Cited US recall lookup for AI agents: CPSC and FDA data, nothing invented.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 332 tokens (~83/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · rattlewatch.rattled.ca
claude mcp add --transport http veritylabsai-rattlewatch 'https://rattlewatch.rattled.ca/mcp'
{
"mcpServers": {
"veritylabsai-rattlewatch": {
"url": "https://rattlewatch.rattled.ca/mcp"
}
}
} {
"servers": {
"veritylabsai-rattlewatch": {
"type": "http",
"url": "https://rattlewatch.rattled.ca/mcp"
}
}
} [mcp_servers.veritylabsai-rattlewatch] url = "https://rattlewatch.rattled.ca/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"veritylabsai-rattlewatch": {
"type": "remote",
"url": "https://rattlewatch.rattled.ca/mcp",
"enabled": true
}
}
} openclaw mcp add veritylabsai-rattlewatch --url 'https://rattlewatch.rattled.ca/mcp' --transport streamable-http
mcp_servers:
veritylabsai-rattlewatch:
url: "https://rattlewatch.rattled.ca/mcp" {
"McpServers": {
"veritylabsai-rattlewatch": {
"Transport": "http",
"Url": "https://rattlewatch.rattled.ca/mcp"
}
}
} assistant mcp add veritylabsai-rattlewatch -t streamable-http -u 'https://rattlewatch.rattled.ca/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://rattlewatch.rattled.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rattlewatch.rattled.ca | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f98700850571075b77304bb956cbb41750 |
| SANs: rattlewatch.rattled.ca | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rattlewatch.rattled.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| rattled.ca. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rattlewatch.rattled.ca/mcp | Verified | 200 | |
| http (plaintext) | http://rattlewatch.rattled.ca/mcp | HTTPS enforced | 301 | https://rattlewatch.rattled.ca/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_requirement ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | – | – | – |
| subject | string | yes | – |
No output schema declared.
No examples provided.
list_changes ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since | string | yes | – |
No output schema declared.
No examples provided.
search_recalls ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| market | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
verify ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
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.