Crimp
REMOTE · CRIMP.STUDIO
Plan DC electrical systems: find components, calculate circuits, check designs and create drafts.
Available components
Last scanned (21 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 4 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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 29 Oct 26 −41
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- “create_draft” added an optional parameter “designProfileId” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 23 Oct 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.
- 21 Oct 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.
- 19 Oct 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.
- 17 Oct 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.
- 15 Oct 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.
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 4 Nov 2026 · Probed https://crimp.studio/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=crimp.studio | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 629ded6a6a6f2ffd13daf030b77d258a |
| SANs: crimp.studio | ||||||
| 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 crimp.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | present | 1354 | 8 | Verified |
| crimp.studio. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="Crimp Professional"
Bearer realm="Crimp Professional"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| www-authenticate | Bearer realm="Crimp Professional" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://crimp.studio/api/mcp | Auth required | 401 | |
| http (plaintext) | http://crimp.studio/api/mcp | HTTPS enforced | 301 | https://crimp.studio/api/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 →
analyze_system ~95
Analyze an explicit current-schema System with Crimp's canonical sizing, diagnostics and energy engine. Read-only. Maximum 40 component nodes, 20 zones and 100 cables. Unknown fields, invalid references and other schema versions are rejected. Results preserve provisional currents, unknown fault protection and estimated inputs; no findings is not certification. No scenario sweep in v1.
| Name | Type | Req | Description |
|---|---|---|---|
| autoSizeTargetPct | – | – | – |
| system | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object | – | – |
| metadata | object | yes | – |
| ok | boolean | yes | – |
| tool | string | yes | – |
No examples provided.
calculate_circuit ~92
Run the existing wire or DC-DC calculator deterministically. Every input field is required: use null for unknown numbers/options and an empty string for missing evidence. Unknown evidence stays unknown. kind=wire requires the wire input shape; kind=dc-dc requires the charger input shape. No fuse selection or installation certification.
| Name | Type | Req | Description |
|---|---|---|---|
| input | – | yes | – |
| kind | string | yes | – |
| units | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object | – | – |
| metadata | object | yes | – |
| ok | boolean | yes | – |
| tool | string | yes | – |
No examples provided.
create_draft ~151
Build and analyze a Crimp planning draft from exact catalog IDs and structured connections, without an AI model call. Agent provides physical lengths and provenance; Crimp selects terminals, layout, wire and fuse suggestions. Display the exact returned reviewUrl as a clickable HTTPS link labeled Review schematic in Crimp; do not substitute a local HTML wrapper. The link opens a view-only preview; Edit a copy is a separate explicit action that creates a new local project. At most 10 counted equipment items, 40 components and 100 cables. Does not save, replace or publish a user's project. Retain assumptions and review findings before installation.
| Name | Type | Req | Description |
|---|---|---|---|
| designProfileId | string | – | – |
| draft | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object | – | – |
| metadata | object | yes | – |
| ok | boolean | yes | – |
| tool | string | yes | – |
No examples provided.
get_component ~45
Read one exact catalog component, including terminal IDs, electrical specs and known configuration. Catalog data does not verify an installed part or its protection evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object | – | – |
| metadata | object | yes | – |
| ok | boolean | yes | – |
| tool | string | yes | – |
No examples provided.
search_components ~76
Search Crimp's catalog by name, manufacturer, model or ID. Returns stable catalog IDs and published component data; use get_component for terminals and full fields. Read-only; no AI model call.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| error | object | – | – |
| metadata | object | yes | – |
| ok | boolean | yes | – |
| tool | string | yes | – |
No examples provided.
How do I install the Crimp MCP server?
Crimp is a hosted endpoint at https://crimp.studio/api/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 · crimp.studio
claude mcp add --transport http studio-crimp-crimp 'https://crimp.studio/api/mcp'
What is the Crimp MCP server?
Crimp is an MCP server listed in the public MCP registry as studio.crimp/crimp. Plan DC electrical systems: find components, calculate circuits, check designs and create drafts. This page covers its hosted endpoint (https://crimp.studio/api/mcp).
Is the Crimp MCP server safe to use?
Crimp scores 33 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 Crimp MCP server expose?
Crimp exposes 5 tools: search_components, get_component, calculate_circuit, analyze_system, create_draft. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.
Does the Crimp MCP server require authentication?
Yes. Crimp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Crimp MCP server still maintained?
Crimp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.