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

plateop-check

https://check.plateop.com

Registry code: f77e6744e4f81025

api record

Free facts about a used car from the official register (NL, GB, IL, IS, DK), each with source and date, and model-wide inspection statistics. Read resource plateop://guide.

endpoint
https://check.plateop.com/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 plateop-check live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is plateop-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does plateop-check have?
2 tools: model_inspection_stats, vehicle_check.
Is plateop-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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
115ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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.

  • model_inspection_stats unknown 1h ago

    Model-wide periodic inspection statistics (how often a make and model fails or gets findings), with source, as-of date and the citation line to use. Not about one specific car: for that use vehicle_check.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "brand",
        "model",
        "country"
      ],
      "properties": {
        "brand": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "Make, for example Volkswagen"
        },
        "model": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "Model, for example Golf"
        },
        "country": {
          "enum": [
            "nl",
            "gb",
            "il",
            "is",
            "dk"
          ],
          "type": "string",
          "description": "Country of the register: nl, gb, il, is or dk"
        },
        "language": {
          "type": "string",
          "pattern": "^[a-z]{2}$",
          "description": "Optional two-letter language for the texts, for example nl, en, he, is, da. Unsupported values fall back to the country's default."
        }
      }
    }
    arguments 39 lines
  • vehicle_check unknown 1h ago

    Free facts about one used car from the official register: vehicle data, periodic inspection due date, odometer verdict, insurance, inspection findings and recalls, each with source and as-of date. Also returns the link where a person can start the full paid report. Countries: nl, gb, il, is, dk.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "plate",
        "country"
      ],
      "properties": {
        "plate": {
          "type": "string",
          "maxLength": 20,
          "minLength": 1,
          "description": "Number plate. Spaces, dashes and case are fine."
        },
        "country": {
          "enum": [
            "nl",
            "gb",
            "il",
            "is",
            "dk"
          ],
          "type": "string",
          "description": "Country of the register: nl, gb, il, is or dk"
        },
        "language": {
          "type": "string",
          "pattern": "^[a-z]{2}$",
          "description": "Optional two-letter language for the texts, for example nl, en, he, is, da. Unsupported values fall back to the country's default."
        }
      }
    }
    arguments 32 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 f77e6744e4f81025.

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