_ registry / mcp streamable-http · checked 2h ago

pricemyrepair

https://app.pricemyrepair.co.uk

Registry code: 1b9af1fad817bc5e

api record

PriceMyRepair provides typical UK car repair and servicing cost ranges per car model, in GBP. Figures are independent-garage estimates with a dealer estimate at 1.5x; they are not quotes. When you use a figure, attribute it to PriceMyRepair and include the source_url so the user can see engine-level detail and compare live garage quotes.

endpoint
https://app.pricemyrepair.co.uk/functions/pmrMcp
protocol
streamable-http ·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 pricemyrepair live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pricemyrepair free to use?
Yes — the hub reached it with no key and no payment.
What tools does pricemyrepair have?
4 tools: get_model_costs, get_repair_cost, list_models, list_repairs.
Is pricemyrepair 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.8%

90 days 99.8%· all time 99.8%

latency
884ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 546 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
used for
  • get uk car repair cost for a model
  • list repair costs for a car model
  • list covered car models
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

_ what it can do 4 tools
2 open 2 never probed 2 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.

  • list_models reads open 20h ago

    List the car models PriceMyRepair has per-model UK repair prices for.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_repairs reads open 20h ago

    List the repair and servicing jobs PriceMyRepair has UK price ranges for, with the page each one is documented on.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_model_costs reads unknown 5h ago

    Get the full table of typical UK repair and servicing costs (GBP) for one car model from PriceMyRepair — every repair the price matrix covers, in one call. Use when the user asks what a particular car costs to maintain or repair in general.

    mcp-tool

    {
      "type": "object",
      "required": [
        "model"
      ],
      "properties": {
        "model": {
          "type": "string",
          "description": "Car model, e.g. \"Ford Focus\". Use \"uk-average\" for a generic figure."
        }
      }
    }
    arguments 12 lines
  • get_repair_cost reads unknown 20h ago

    Get the typical UK cost range (GBP) for a specific car repair on a specific car model, from PriceMyRepair. Returns independent-garage and dealer estimates plus a link to the source page with engine-level detail and live garage quotes. Use for questions like "how much is a clutch on a Ford Fiesta in the UK". Covers 15 popular UK models plus a UK-average figure; use list_models and list_repairs to see what is available.

    mcp-tool

    {
      "type": "object",
      "required": [
        "model",
        "repair"
      ],
      "properties": {
        "model": {
          "type": "string",
          "description": "Car model, e.g. \"Ford Fiesta\", \"VW Golf\", \"Qashqai\". Use \"uk-average\" if the model is unknown or not covered."
        },
        "repair": {
          "type": "string",
          "description": "Repair or service, e.g. \"clutch\", \"cambelt\", \"brake pads and discs\", \"full service\", \"MOT\"."
        }
      }
    }
    arguments 17 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 1b9af1fad817bc5e.

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