partreel
Registry code: 47c2985f5a342743
PartReel: registry of verified KiCad parts (footprint/symbol/3D). search_parts -> get_part -> download URLs. All assets CC-BY-4.0, no auth.
- endpoint
- https://mcp.partreel.com/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 partreel live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is partreel free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does partreel have?
- 7 tools: how_to_contribute, search_parts, report_feedback, request_part, submit_part, get_part, list_parts.
- Is partreel 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.2%· all time 99.2%
last good check
of 7 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- iot & hardware
- used for
- search verified kicad component parts
- get kicad footprint and symbol downloads
- request generation of a new part
- submit a kicad part
- takes → gives
- text → data
- tools
- 4 reads3 changes data
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_parts reads open 15h ago
List all parts in the registry (id, name, family, pins).
{ "type": "object", "properties": {} }arguments 4 lineshow_to_contribute reads unknown never probed
Get machine-readable instructions for adding a new part to the registry (file layout, metadata schema, quality gates, PR process). Use when a part is missing.
{ "type": "object", "properties": {} }arguments 4 linessearch_parts reads unknown 15h ago
Search the PartReel registry of verified KiCad components (footprint + symbol + 3D STEP/GLB, no login, CC-BY-4.0). Returns matching parts with ids. Use get_part for download URLs. Example queries: 'usb-c', 'jst ph 4pin', 'esp32', 'microsd', 'screw terminal'.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Search text (name, family, keywords, pin count)" } } }arguments 12 linesreport_feedback changes data unknown never probed
Report real-world usage feedback for a part (e.g. 'fabricated 5 boards at JLCPCB, footprint fit perfectly' or 'pad 3 misaligned'). Feedback is recorded publicly on GitHub and builds the part's field-proven trust score. Please report after actually using a part — both successes and problems help.
{ "type": "object", "required": [ "part_id", "result", "notes" ], "properties": { "notes": { "type": "string", "description": "Details: what you built, fab house, what worked or what was wrong (max 1000 chars)" }, "result": { "enum": [ "worked", "problem" ], "type": "string", "description": "'worked' = used successfully, 'problem' = issue found" }, "part_id": { "type": "string", "description": "Part id, e.g. 'jst_ph_4pin'" } } }arguments 26 linesrequest_part changes data unknown never probed
Request on-demand generation of a parametric part that isn't in the registry yet. The registry generates it (footprint+symbol+3D), runs quality gates, and publishes it within ~5 minutes. Pin-count families (use 'pins'): pin_header_254 (2.54mm), pin_header_200 (2.0mm), pin_header_127 (1.27mm) — pins 1-40. Variant families (use 'variant'): ht73xx (LDO Vout code: 7318,7325,7327,7330,7333,7335,7341,7350), ht78xx (7818,7825,7827,7830,7833,7850), sy8008 (grade a/b/c = 0.6A/1A/1.2A), max1704x (17048,17049). Always try get_part / search_parts first.
{ "type": "object", "required": [ "family" ], "properties": { "pins": { "type": "integer", "maximum": 40, "minimum": 1, "description": "for pin_header_* families" }, "family": { "enum": [ "pin_header_254", "pin_header_200", "pin_header_127", "ht73xx", "ht78xx", "sy8008", "max1704x" ], "type": "string" }, "variant": { "type": "string", "description": "for variant families (e.g. '7350', 'a', '17049')" } } }arguments 30 linessubmit_part changes data unknown never probed
Upload a part you built so it is SHARED IMMEDIATELY (status 'staging', unverified). It becomes searchable and downloadable right away; hourly CI then runs the full quality gates and opens a PR to promote it to the verified registry. Provide the full text of the .kicad_sym and .kicad_mod files plus metadata. Cite real datasheet dimensions in dimensions_source — copies of the official KiCad (CC-BY-SA) library are auto-rejected at promotion.
{ "type": "object", "required": [ "id", "name", "description", "category", "license", "dimensions_source", "symbol", "footprint" ], "properties": { "id": { "type": "string", "description": "part id: lowercase letters/digits/underscore, 3-64 chars, e.g. 'ti_sn74lvc1g08_sot23'" }, "name": { "type": "string", "description": "human-readable name / MPN" }, "symbol": { "type": "string", "description": "full .kicad_sym file text" }, "license": { "type": "string", "description": "CC-BY-4.0 for original work; MIT/Apache-2.0/CERN-OHL-P/CC-BY for imports" }, "category": { "type": "string", "description": "one of: connector, discrete, ic, passive, switch, module, etc" }, "datasheet": { "type": "string", "description": "datasheet URL (optional)" }, "footprint": { "type": "string", "description": "full .kicad_mod file text" }, "description": { "type": "string" }, "dimensions_source": { "type": "string", "description": "datasheet URL + page/figure the dimensions came from (min 20 chars)" } } }arguments 50 linesget_part reads unknown 15h ago
Get full detail for one part by id: parameters, verification status, datasheet, and absolute download URLs for .kicad_mod (footprint), .kicad_sym (symbol), .step and .glb (3D).
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Part id, e.g. 'jst_ph_4pin', 'usb_c_16p'" } } }arguments 12 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 id47c2985f5a342743.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/47c2985f5a342743/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/47c2985f5a342743?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.