Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rattlewatch

REMOTE · RATTLEWATCH.RATTLED.CA

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

−84 this week 0 Trust /100

Last scanned (7 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 7 Nov 2026.

Category Health and Science

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 14 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 12 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 11 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 10 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 8 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 14 Nov 2026 · Probed https://rattlewatch.rattled.ca/mcp

TLS unreached
DNSSEC insecure

Validation of rattlewatch.rattled.ca. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ca. DS published 26384 13 Verified
rattled.ca. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
http (plaintext) http://rattlewatch.rattled.ca/mcp HTTPS enforced
MCP tools · 4 exposed · ~332 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
market–––
subjectstringyes–

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.

NameTypeReqDescription
limitinteger––
sincestringyes–

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.

NameTypeReqDescription
limitinteger––
marketstring––
querystringyes–

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.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

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.

remote · rattlewatch.rattled.ca

# add to Claude Code
claude mcp add --transport http veritylabsai-rattlewatch 'https://rattlewatch.rattled.ca/mcp'
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 0 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?

Its publisher declares no required credentials for Rattlewatch. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Rattlewatch MCP server still maintained?

Rattlewatch has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Rattlewatch MCP server?

VerifyMCP ran 3 checks on Rattlewatch, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Rattlewatch: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.