rockauto
https://rockauto-mcp.b-a92.workers.dev
Registry code: 405a19f9ca5baf00
Search and browse the RockAuto auto parts catalog with pricing and vehicle compatibility.
from a public catalogue that lists it, not from the operator
- endpoint
- https://rockauto-mcp.b-a92.workers.dev/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 rockauto live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is rockauto free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rockauto have?
- 10 tools: search_parts, list_engines, search_part_number, list_models, list_years, browse_category, get_part_details, get_parts, ….
- Is rockauto 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.
90 days 99.8%· all time 99.8%
last good check
of 10 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- search auto parts for a vehicle
- look up a part number
- get part details and pricing
- browse parts categories by vehicle
- takes → gives
- text → data
- tools
- 10 reads
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.
through this hub
successful
what callers paid
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_makes reads open 2h ago
List all vehicle makes (manufacturers) available on RockAuto. Returns make names that can be used with list_years.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessearch_parts reads unknown 6h ago
Search for parts by vehicle and part type in one step. Automatically navigates the catalog hierarchy to find matching parts. Use simple part type keywords like "brake pad", "oil filter", "alternator", "spark plug", etc. Returns parts with direct RockAuto catalog links.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "make", "year", "model", "partType" ], "properties": { "make": { "type": "string", "description": "Vehicle make, e.g. \"Honda\", \"Toyota\", \"Ford\"" }, "year": { "type": "string", "description": "Model year, e.g. \"2020\"" }, "model": { "type": "string", "description": "Vehicle model, e.g. \"Civic\", \"Camry\", \"F-150\"" }, "partType": { "type": "string", "description": "Part type to search for, e.g. \"brake pad\", \"oil filter\", \"alternator\", \"spark plug\", \"strut\"" } } }arguments 28 lineslist_engines reads unknown 16h ago
List engine options for a specific vehicle. Returns engine descriptions and their carcode IDs needed for browsing parts.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "make", "year", "model" ], "properties": { "make": { "type": "string", "description": "Vehicle make, e.g. \"Honda\"" }, "year": { "type": "string", "description": "Model year, e.g. \"2020\"" }, "model": { "type": "string", "description": "Vehicle model, e.g. \"Civic\"" } } }arguments 23 linessearch_part_number reads unknown 9h ago
Search RockAuto by a specific part number. Supports wildcards (*). Example: "GNAD2102C" or "15400-PLM-A02".
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "partNumber" ], "properties": { "partNumber": { "type": "string", "description": "Part number to search for, e.g. \"GNAD2102C\". Supports * wildcards." } } }arguments 13 lineslist_models reads unknown 16h ago
List all models for a given make and year. Use results from list_makes and list_years.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "make", "year" ], "properties": { "make": { "type": "string", "description": "Vehicle make, e.g. \"Honda\"" }, "year": { "type": "string", "description": "Model year, e.g. \"2020\"" } } }arguments 18 lineslist_years reads unknown 16h ago
List all available model years for a vehicle make. Use a make name from list_makes.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "make" ], "properties": { "make": { "type": "string", "description": "Vehicle make, e.g. \"Honda\", \"Toyota\", \"Ford\"" } } }arguments 13 linesbrowse_category reads unknown 9h ago
Browse a RockAuto catalog URL to see subcategories or parts. Use URLs returned by list_categories or previous browse_category calls. Returns navigation links (subcategories/part types) and any parts found at that level.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "A RockAuto catalog URL from a previous tool result" } } }arguments 14 linesget_part_details reads unknown 9h ago
Get detailed information about a specific part using its more-info URL from a previous search or parts listing.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "The moreInfoUrl from a parts listing or search result" } } }arguments 14 linesget_parts reads unknown 2h ago
Get parts listed on a RockAuto catalog page. Provide the URL of a part type page (the deepest level in the catalog hierarchy). Returns manufacturer, part number, price, and description for each part.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "URL of a RockAuto part type page from browse_category results" } } }arguments 14 lineslist_categories reads unknown 2h ago
List part categories for a specific vehicle. Requires the engine description and carcode from list_engines.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "make", "year", "model", "engine", "carcode" ], "properties": { "make": { "type": "string", "description": "Vehicle make, e.g. \"Honda\"" }, "year": { "type": "string", "description": "Model year, e.g. \"2020\"" }, "model": { "type": "string", "description": "Vehicle model, e.g. \"Civic\"" }, "engine": { "type": "string", "description": "Engine description from list_engines, e.g. \"2.0L L4\"" }, "carcode": { "type": "string", "description": "Carcode from list_engines, e.g. \"3445241\"" } } }arguments 33 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id405a19f9ca5baf00.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/405a19f9ca5baf00/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/405a19f9ca5baf00?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.