mcp-registry/io.github.mingyo186/partreel · v1.0.0
As of 2026-10-22 02:54 UTC, the Mingyo186 Partreel MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Verified KiCad footprints, symbols & 3D models for AI agents. No signup, CC-BY-4.0, quality-gated.
Claude Code
claude mcp add --transport http mingyo186-partreel-mcp-server https://mcp.partreel.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mingyo186-partreel-mcp-server": {
"type": "http",
"url": "https://mcp.partreel.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mingyo186%2Fpartreel/fixes
{
"name": "get_part",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Part id, e.g. 'jst_ph_4pin', 'usb_c_16p'"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_parts",
"description": "List all parts in the registry (id, name, family, pins).",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_parts",
"description": "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'.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Search text (name, family, keywords, pin count)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mingyo186/partreel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mingyo186/partreel"}) over MCP.
submit_part ~392 tokensrequest_part ~256 tokensreport_feedback ~208 tokenssearch_parts ~127 tokensget_part ~100 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.mingyo186%2Fpartreel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mingyo186%2Fpartreel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mingyo186%2Fpartreel.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mingyo186%2Fpartreel.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mingyo186%2Fpartreel?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:328926d9e3672e3f…, first seen 2026-10-17, included at leaf 10139 of 43,117. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable other servers · most reliable search servers · most reliable files servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 02:54 UTC, the Mingyo186 Partreel MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mingyo186 Partreel MCP server advertises 7 tools, including get_part, how_to_contribute, list_parts, report_feedback, request_part.
Point your MCP client at this streamable-http endpoint: https://mcp.partreel.com/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.