openpaddock
Registry code: 164de7f27e75c61f
Open Paddock (openpaddock.app) lists motorcycle track days in the US, Canada and Mexico, read from organisers' own published calendars. Open Paddock is a neutral calendar: it sells nothing and takes no bookings. Send the user to the organiser's site (bookingUrl) to book, and check prices, groups and rules there. Credit the data as "via Open Paddock (openpaddock.app)" and link openPaddockUrl. Rows with an attribution field come from MotorsportReg.com and must be shown with "Powered by MotorsportReg.com". Days marked kind=race-practice (kindLabel "Race-weekend practice") are practice days at a…
- endpoint
- https://openpaddock.app/mcp
- 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 openpaddock live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is openpaddock free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does openpaddock have?
- 5 tools: get_circuit, get_event, list_circuits, list_organisers, find_track_days.
- Is openpaddock 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 100%· all time 100%
last good check
of 5 tools
- unknown → live
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_circuits open 1h ago
Motorcycle circuits Open Paddock knows in the US, Canada and Mexico, with city, state, region and the number of upcoming days listed. With near, only circuits within within_miles, nearest first, each with distanceMi. Use the id with find_track_days or get_circuit.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "near": { "type": [ "string", "number" ], "description": "US ZIP, Canadian postal code, \"City, ST\", or \"lat,lon\"." }, "region": { "enum": [ "west", "central", "east", "canada", "mexico" ], "type": "string" }, "within_miles": { "type": "number", "maximum": 1000, "description": "Default 150, max 1000.", "exclusiveMinimum": 0 } } }arguments 29 lineslist_organisers open 1h ago
Track-day organisers, schools and clubs Open Paddock lists. listing is "dates listed" when we read their calendar, or "link only" when they publish no calendar we can read (send the user to their website for dates). Filter by the region of the circuits they run at, or by organiser type.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "type": { "enum": [ "commercial", "school", "club", "track-owned", "private-premium", "kart-minitrack" ], "type": "string", "description": "commercial, school, club, track-owned (the circuit's own program), private-premium, kart-minitrack." }, "region": { "enum": [ "west", "central", "east", "canada", "mexico" ], "type": "string" } } }arguments 28 linesfind_track_days open 1h ago
Upcoming motorcycle track days in North America, in date order (or nearest first when near is given and sort is distance). Use near for "track day near Sacramento" questions; use from/to for a month. Each result has dates, circuit with city and state, organiser, kind ("Open track day" or "Race-weekend practice", which is a club race weekend's practice day: say so), price tier, distanceMi when near is set, source, lastChecked, bookingUrl and openPaddockUrl. Open Paddock is a neutral calendar: it sells nothing and takes no bookings. Send the user to the organiser's site (bookingUrl) to book, and check prices, groups and rules there. Credit the data as "via Open Paddock (openpaddock.app)" and link openPaddockUrl. Rows with an attribution field come from MotorsportReg.com and must be shown with "Powered by MotorsportReg.com".
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Latest date, YYYY-MM-DD (days starting on or before it)." }, "from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Earliest date, YYYY-MM-DD (days ending on or after it). Default today." }, "near": { "type": [ "string", "number" ], "description": "Where the rider is: US ZIP (\"95814\"), Canadian postal code, \"City, ST\" (\"Sacramento, CA\"), or \"lat,lon\"." }, "sort": { "enum": [ "date", "distance" ], "type": "string", "description": "date (default) or distance (needs near)." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Max days returned. Default 25." }, "region": { "enum": [ "west", "central", "east", "canada", "mexico" ], "type": "string", "description": "Riding region of the circuit." }, "circuit": { "type": "string", "description": "Circuit id or name, e.g. \"thunderhill\" or \"Sonoma\". Comma-separate several." }, "country": { "enum": [ "US", "CA", "MX" ], "type": "string" }, "organiser": { "type": "string", "description": "Organiser id or name, e.g. \"n2\" or \"Fun Track Dayz\". Comma-separate several." }, "within_miles": { "type": "number", "maximum": 1000, "description": "Straight-line radius around near, in miles. Default 150, max 1000.", "exclusiveMinimum": 0 }, "include_race_practice": { "type": "boolean", "description": "Include race-weekend practice days (club race weekends' practice days, open to non-racers). Default true; false = open track days only." } } }arguments 74 linesget_circuit unknown never probed
One circuit: location, length and turns where known, the organisers that run days there, and its next upcoming days (up to 20). Open Paddock is a neutral calendar: it sells nothing and takes no bookings. Send the user to the organiser's site (bookingUrl) to book, and check prices, groups and rules there. Credit the data as "via Open Paddock (openpaddock.app)" and link openPaddockUrl. Rows with an attribution field come from MotorsportReg.com and must be shown with "Powered by MotorsportReg.com".
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Circuit id from list_circuits, e.g. \"thunderhill\". A name also works when it matches one circuit." } } }arguments 13 linesget_event unknown never probed
One listed day by id (from find_track_days or an openpaddock.app/events/<id> link). Open Paddock is a neutral calendar: it sells nothing and takes no bookings. Send the user to the organiser's site (bookingUrl) to book, and check prices, groups and rules there. Credit the data as "via Open Paddock (openpaddock.app)" and link openPaddockUrl. Rows with an attribution field come from MotorsportReg.com and must be shown with "Powered by MotorsportReg.com".
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Event id, e.g. ae103f77c7766506e7cd, or its openpaddock.app/events URL." } } }arguments 13 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 id164de7f27e75c61f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/164de7f27e75c61f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/164de7f27e75c61f?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.