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

VIN Recall MCP

https://vin-recall-mcp.zenithserver.duckdns.org

Registry code: a75886d84815c1da

api record

Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.

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

endpoint
https://vin-recall-mcp.zenithserver.duckdns.org/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 VIN Recall MCP live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is VIN Recall MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does VIN Recall MCP have?
2 tools: check_recalls, decode_vin.
Is VIN Recall MCP 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
99.7%

90 days 99.6%· all time 99.6%

latency
621ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 496 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • decode a vin
  • check open recalls for a vin
takes → gives
text → data
tools
2 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 2 tools
2 never probed 0 of 2 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.

  • check_recalls reads unknown 10h ago

    List open safety recall campaigns for a vehicle by VIN, using the NHTSA Recalls database. Decodes the VIN internally to get make/model/year, then looks up campaigns for that vehicle configuration. Important: results are recall campaigns issued for the make/model/year configuration — this does NOT confirm whether this specific VIN's vehicle was actually repaired at a dealer. Always describe results as 'open recall campaigns for this vehicle,' never as whether the car 'is' or 'isn't' fixed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vin"
      ],
      "properties": {
        "vin": {
          "type": "string",
          "description": "A 17-character US vehicle VIN (letters and digits, excluding I, O, and Q). The VIN is decoded internally to determine make/model/year for the recall lookup."
        }
      }
    }
    arguments 13 lines
  • decode_vin reads unknown 10h ago

    Decode a 17-character US vehicle VIN into make, model, year, body class, engine cylinders, fuel type, drive type, and assembly plant country, using the NHTSA vPIC database. Covers US-market vehicles built from 1981 onward (the 17-character VIN standard); pre-1981 and some foreign-market vehicles may return partial or no data. Decoded fields are manufacturer-submitted and individual fields may be missing even for a successfully decoded VIN.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vin"
      ],
      "properties": {
        "vin": {
          "type": "string",
          "description": "A 17-character US vehicle VIN (letters and digits, excluding I, O, and Q)."
        }
      }
    }
    arguments 13 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 a75886d84815c1da.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a75886d84815c1da/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/a75886d84815c1da/badge.svg)](https://brick.blue/agent/a75886d84815c1da?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
60%

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.

_ also on duckdns.org 11 entries

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.

3 more sit on this domain. All of them.