Schematik
REMOTE · WWW.SCHEMATIK.IO
Search electronics parts and step-by-step hardware build guides from Schematik.
Available components
Last scanned (44 minutes ago)
Scores higher than 74% of remote servers
Reachable. Last reached 22 Nov 2026.
Category IoT and Hardware
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 520 tokens (~130/item across 4 items; 4 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +5
- Tool “get_part” rewrote its description, which is the text the model reads security
- Tool “search_build_guides” rewrote its description, which is the text the model reads security
- Tool “search_parts” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → good functional
- “get_build_guide” reworded the description of “slug” cosmetic
- “get_part” reworded the description of “slug” cosmetic
- “search_build_guides” reworded the description of “board” cosmetic
- “search_build_guides” reworded the description of “limit” cosmetic
- “search_build_guides” reworded the description of “query” cosmetic
- “search_parts” reworded the description of “limit” cosmetic
- “search_parts” reworded the description of “query” cosmetic
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 68
First indexed and scored.
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 22 Nov 2026 · Probed https://www.schematik.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.schematik.io | CN=YR2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | RSA 2048 | SHA256-RSA | 5bf7eba3cb3ee5efff0b78d43c28033640c |
| SANs: *.schematik.io, schematik.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.schematik.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| schematik.io. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.schematik.io/mcp | Verified | 200 | |
| http (plaintext) | http://www.schematik.io/mcp | HTTPS enforced | 308 | https://www.schematik.io/mcp |
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 →
get_build_guide Get build guide ~57
A published build guide by slug as markdown: parts, assembly steps, connections and firmware.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The guide's slug as returned by search_build_guides, e.g. 'build-a-co2-room-monitor'. |
No output schema declared.
No examples provided.
get_part Get part ~113
One part from the catalogue by slug, as JSON: name, brand, part number, description, category, an available vendor price (lowest offer in one currency, USD when available, e.g. 'from 4.5 USD'), pinout and a link to its Schematik page. Brand, part number, description, price and pinout can be null when unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The part's slug as returned by search_parts, e.g. 'bme280-i2c-sensor'. |
No output schema declared.
No examples provided.
search_build_guides Search build guides ~146
Search published Schematik build guides: complete projects with parts, wiring and firmware. Leave query empty to list featured guides first. Returns a JSON list of guides with a link and a remixUrl; pass a result's slug to get_build_guide for the full guide.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Only return guides for this board. Omit for all boards. |
| limit | integer | – | How many guides to return at most. Fewer come back when fewer guides match. |
| query | string | – | What the project should do or use, matched against guide titles, descriptions and boards, e.g. 'weather station'. Leave empty to browse guides, featured ones first. |
No output schema declared.
No examples provided.
search_parts Search parts ~130
Search Schematik's public electronics parts catalogue (boards, sensors, displays, modules) by name, brand, part number or use. Returns a JSON list of parts, best matches first; pass a result's slug to get_part for its pinout and price.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many parts to return at most. Fewer come back when fewer parts match. |
| query | string | yes | Words to match, e.g. a part name, brand, part number or use such as 'BME280' or 'oled display'. Parts matching any word are returned, best matches first. |
No output schema declared.
No examples provided.
How do I install the Schematik MCP server?
Schematik is a hosted endpoint at https://www.schematik.io/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 · www.schematik.io
claude mcp add --transport http io-schematik-schematik 'https://www.schematik.io/mcp'
What is the Schematik MCP server?
Schematik is an MCP server listed in the public MCP registry as io.schematik/schematik. Search electronics parts and step-by-step hardware build guides from Schematik. This page covers its hosted endpoint (https://www.schematik.io/mcp).
Is the Schematik MCP server safe to use?
Schematik scores 79 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 Schematik MCP server expose?
Schematik exposes 4 tools: search_parts, get_part, search_build_guides, get_build_guide. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.
Does the Schematik MCP server require authentication?
No. We connected to Schematik without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Schematik MCP server still maintained?
Schematik is still listed as active in the MCP registry. We last reached this channel on 22 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 Schematik MCP server?
VerifyMCP ran 13 checks on Schematik, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.