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

Dutch Vehicle Context

https://vehicle-context.tradebrite.nl

Registry code: f90a6a799b4f8f41

api record

Dutch vehicle report by licence plate: MOT, defects, odometer verdict and open recalls.

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

endpoint
https://vehicle-context.tradebrite.nl/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 Dutch Vehicle Context live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is Dutch Vehicle Context free to use?
Yes — the hub reached it with no key and no payment.
What tools does Dutch Vehicle Context have?
1 tool: get_verified_vehicle_context.
Is Dutch Vehicle Context 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 100%· all time 100%

latency
490ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 268 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get a dutch vehicle report by licence plate
  • check mot, odometer and recalls for a car
takes → gives
text → data
tools
1 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 1 tools
1 never probed 0 of 1 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.

  • get_verified_vehicle_context reads unknown 6h ago

    Geeft de geverifieerde context van een Nederlands voertuig op kenteken, uit het openbare kentekenregister en het terugroepregister. Gebruik dit bij elke vraag over een concrete Nederlandse auto, motor, bestelbus of aanhanger — bijvoorbeeld bij het beoordelen van een occasion, het controleren van de APK, of de vraag of er een terugroepactie openstaat. Het antwoord heeft deze blokken: `identity` (merk, type, bouwjaar, leeftijd), `technical`, `fuel` (brandstof en emissieklasse), `inspection` (APK met historie), `defects` (afkeurpunten per keuring, mét terugkerende gebreken), `odometer` (oordeel over de kilometerstand), `recalls` (terugroepacties, open én afgehandeld, met defect, gevolg, gevaar en herstel), `status_flags`, `value`, `signals` en `provenance`. `signals` zijn observaties, geen vastgestelde gebreken. Ze staan gesorteerd op ernst; begin daarmee. Let vooral op `open_recall`, `odometer_illogical` en `recurring_defect` — dat laatste betekent dat hetzelfde punt bij meerdere keuringen is afgekeurd. BELANGRIJK, twee dingen. Ten eerste: als `identity.found` false is, bestaat het kenteken niet in het register en gaat de rest van het antwoord nergens over; meld dat dan in plaats van lege velden te presenteren. Ten tweede: of een voertuig als gestolen of vermist geregistreerd staat is NIET openbaar en staat hier dus niet in. Een rapport zonder diefstalmelding is geen bewijs dat een voertuig niet gestolen is — zeg dat er expliciet bij als iemand naar de betrouwbaarheid van een aankoop vraagt. Dit is geen taxatie, geen technische keuring en geen aankoopadvies.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "plate"
      ],
      "properties": {
        "depth": {
          "enum": [
            "compact",
            "full"
          ],
          "type": "string",
          "description": "Hoeveel detail. 'compact' (standaard) geeft alleen de laatste keuring en kort de afgehandelde terugroepacties in; alle feiten en álle signalen blijven erin, en een openstaande terugroepactie blijft altijd volledig. Vraag 'full' voor de complete keuringshistorie en de bron-URL's."
        },
        "plate": {
          "type": "string",
          "minLength": 6,
          "description": "Nederlands kenteken, met of zonder streepjes: '01-TH-FD', '01THFD' of '01 th fd' werken allemaal. Zes tekens."
        }
      }
    }
    arguments 22 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 f90a6a799b4f8f41.

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

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 tradebrite.nl 1 entry

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.