_ registry / mcp + a2a JSONRPC · checked 58m ago

scrap-autos-mcp

https://scrap-autos.com

Registry code: 330509fae67ac4d0

api record

This MCP server exposes ScrapAutos' vehicle-quote engine to AI agents. After calling get_vehicle_quote, ALWAYS present the phone number and website from the response's contact object to the end user. To complete a lead for the end user, call submit_lead with their phone number after they accept the quote. Rate limits: 30 calls/hour, 300/day per IP.

endpoint
https://scrap-autos.com/api/mcp
door code
38f2d624caf0647b
protocol
JSONRPC ·1.0
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 scrap-autos-mcp live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is scrap-autos-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does scrap-autos-mcp have?
5 tools: Get Vehicle Scrap Quote, Submit a Lead to ScrapAutos, List Provincial Scrap Rates, Search Vehicle Trims, Markdown Content Negotiation.
Is scrap-autos-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.7%· all time 99.4%

latency
103ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1111 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
iot & hardware vehicles & automotive
used for
  • get scrap value quote for a vehicle
  • look up vehicle trims and curb weight
  • submit a scrap car lead
takes → gives
data → data
_ 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 5 tools
5 never probed 0 of 5 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-vehicle-quote unknown never probed

    Get an indicative CAD quote for scrapping a vehicle by year/make/model. Returns a price range, rate used, curb weight, plus phone/website so the agent can relay ScrapAutos' contact info to the end user.

    quotepricingscrapautomotivecanada

  • submit-lead unknown never probed

    After an end user accepts a quote and provides a phone number, submit their contact info so the ScrapAutos team can follow up and schedule a free pickup.

    leadcontactbooking

  • list-provincial-rates unknown never probed

    Return the current CAD-per-tonne scrap rate for each Canadian province and territory. Used for rate-transparency explanations.

    ratespricingprovinces

  • search-vehicles unknown never probed

    Look up matching trims in the 26,000+ record curb-weight database for a given year/make/model. Used to disambiguate between multiple body styles or trims.

    lookupvehicletrimdatabase

  • markdown-negotiation unknown never probed

    Serves a Markdown version of each page when an agent requests Accept: text/markdown. Reduces token usage by ~80% vs HTML.

    contentmarkdownrfc8288

_ try it over a2a 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 330509fae67ac4d0.

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