safe-check
https://safecheck.dropwatchhq.com
Registry code: 922035fb74a966e9
Is it recalled or fake? Recall lookup vs live US gov feeds + transparent counterfeit risk signal.
from a public catalogue that lists it, not from the operator
- endpoint
- https://safecheck.dropwatchhq.com/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is safe-check live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is safe-check free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does safe-check have?
- 3 tools: counterfeit_risk, recall_lookup, safe_check.
- Is safe-check 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.
90 days 99.8%· all time 99.8%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- look up product recalls
- assess counterfeit risk of a listing
- screen a product for safety
- takes → gives
- text → data
- tools
- 3 reads
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.
through this hub
successful
what callers paid
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.
recall_lookup reads open 15h ago
Look up active US product recalls for a product or brand against live government feeds (CPSC/FDA/NHTSA-style aggregate). Returns matching recalls with the official agency source link and last-updated date. Use to check if something is recalled before buying/using it.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Product name or brand, e.g. 'Peloton bike' or 'stroller'." } } }arguments 12 linessafe_check reads open 15h ago
Run both a recall lookup and a counterfeit-risk check in one call. Best general-purpose product-safety screen.
{ "type": "object", "required": [ "query" ], "properties": { "price": { "type": "number" }, "query": { "type": "string" }, "marketplace": { "type": "string" } } }arguments 17 linescounterfeit_risk reads unknown never probed
Assess counterfeit RISK for a collectible listing (a risk SIGNAL, never proof of fake). Combines marketplace base-risk + a price-vs-retail-median check when the item is a known collectible niche. Returns a risk level (low/med/high), a score, the signals, and authenticity advice.
{ "type": "object", "required": [ "query" ], "properties": { "price": { "type": "number", "description": "Optional: the listed price to compare against the retail median." }, "query": { "type": "string", "description": "Product or brand, e.g. 'Funko Batman' or 'LEGO 10307'." }, "marketplace": { "type": "string", "description": "Optional: where it's listed, e.g. 'aliexpress', 'ebay', 'etsy'." } } }arguments 20 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id922035fb74a966e9.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/922035fb74a966e9/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/922035fb74a966e9?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- qualify.dropwatchhq.com dreamqualify
- freight.dropwatchhq.com freight-intel
- parceledge.dropwatchhq.com parcel-edge
- abc.dropwatchhq.com distress-abc
- diligence.dropwatchhq.com distress-diligence
- oracle.dropwatchhq.com hobby-market-oracle
- research.dropwatchhq.com research-intel
- filings.dropwatchhq.com sec-intel
27 more sit on this domain. All of them.