_ registry / mcp http-sse · checked 7h ago

rattlewatch

https://verity-mcp-243195959173.us-central1.run.app

Registry code: b1a2476050cd8948

api record

Cited product-compliance ground truth for AI agents. Never generates; always cites.

from a public catalogue that lists it, not from the operator

endpoint
https://verity-mcp-243195959173.us-central1.run.app/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is rattlewatch live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is rattlewatch free to use?
Yes — the hub reached it with no key and no payment.
What tools does rattlewatch have?
4 tools: search_recalls, verify, list_changes, get_requirement.
Is rattlewatch safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
157ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 376 checks · signed record
_ what it is for
used for
  • search us product recalls
  • get market-entry requirements for a product
  • verify a product claim against cited records
  • list recent recall changes
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_recalls reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "search_recallsArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 10
        },
        "query": {
          "type": "string",
          "title": "Query"
        },
        "market": {
          "type": "string",
          "title": "Market",
          "default": "US"
        }
      }
    }
    arguments 23 lines
  • verify reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "verifyArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query"
        }
      }
    }
    arguments 13 lines
  • list_changes reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "list_changesArguments",
      "required": [
        "since"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 100
        },
        "since": {
          "type": "string",
          "title": "Since"
        }
      }
    }
    arguments 18 lines
  • get_requirement reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "get_requirementArguments",
      "required": [
        "subject"
      ],
      "properties": {
        "market": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Market",
          "default": null
        },
        "subject": {
          "type": "string",
          "title": "Subject"
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b1a2476050cd8948.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b1a2476050cd8948/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b1a2476050cd8948/badge.svg)](https://brick.blue/agent/b1a2476050cd8948?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.