Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mingyo186/partreel

REMOTE · MCP.PARTREEL.COM

Verified KiCad footprints, symbols & 3D models for AI agents. No signup, CC-BY-4.0, quality-gated.

Available components

0 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 979 tokens (~139/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.partreel.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=partreel.com CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 616dd68a19888fd30ea51af11daf7971
SANs: partreel.com, mcp.partreel.com, *.mcp.partreel.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.partreel.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
partreel.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.partreel.com/mcp Verified 200
http (plaintext) http://mcp.partreel.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~935 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_part ~84

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).

NameTypeReqDescription
idstringyesPart id, e.g. 'jst_ph_4pin', 'usb_c_16p'

No output schema declared.

No examples provided.

how_to_contribute ~42

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_parts ~23

List all parts in the registry (id, name, family, pins).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

report_feedback ~144

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.

NameTypeReqDescription
notesstringyesDetails: what you built, fab house, what worked or what was wrong (max 1000 chars)
part_idstringyesPart id, e.g. 'jst_ph_4pin'
resultstringyes'worked' = used successfully, 'problem' = issue found

No output schema declared.

No examples provided.

request_part ~244

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.

NameTypeReqDescription
familystringyes–
pinsinteger–for pin_header_* families
variantstring–for variant families (e.g. '7350', 'a', '17049')

No output schema declared.

No examples provided.

search_parts ~104

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'.

NameTypeReqDescription
querystringyesSearch text (name, family, keywords, pin count)

No output schema declared.

No examples provided.

submit_part ~294

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.

NameTypeReqDescription
categorystringyesone of: connector, discrete, ic, passive, switch, module, etc
datasheetstring–datasheet URL (optional)
descriptionstringyes–
dimensions_sourcestringyesdatasheet URL + page/figure the dimensions came from (min 20 chars)
footprintstringyesfull .kicad_mod file text
idstringyespart id: lowercase letters/digits/underscore, 3-64 chars, e.g. 'ti_sn74lvc1g08_sot23'
licensestringyesCC-BY-4.0 for original work; MIT/Apache-2.0/CERN-OHL-P/CC-BY for imports
namestringyeshuman-readable name / MPN
symbolstringyesfull .kicad_sym file text

No output schema declared.

No examples provided.

Install

How do I install the io.github.mingyo186/partreel MCP server?

io.github.mingyo186/partreel is a hosted endpoint at https://mcp.partreel.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.partreel.com

# add to Claude Code
claude mcp add --transport http mingyo186-partreel 'https://mcp.partreel.com/mcp'
Common questions

What is the io.github.mingyo186/partreel MCP server?

io.github.mingyo186/partreel is an MCP server listed in the public MCP registry as io.github.mingyo186/partreel. Verified KiCad footprints, symbols & 3D models for AI agents. No signup, CC-BY-4.0, quality-gated. This page covers its hosted endpoint (https://mcp.partreel.com/mcp).

Is the io.github.mingyo186/partreel MCP server safe to use?

io.github.mingyo186/partreel scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mingyo186/partreel MCP server expose?

io.github.mingyo186/partreel exposes 7 tools: search_parts, get_part, list_parts, report_feedback, request_part, and 2 more. Their descriptions and schemas cost roughly 935 tokens of context every time the server is loaded.

Does the io.github.mingyo186/partreel MCP server require authentication?

No. We connected to io.github.mingyo186/partreel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.mingyo186/partreel MCP server still maintained?

io.github.mingyo186/partreel is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.mingyo186/partreel MCP server?

VerifyMCP ran 11 checks on io.github.mingyo186/partreel, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.mingyo186/partreel: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.