# Crimp (remote · crimp.studio)

Plan DC electrical systems: find components, calculate circuits, check designs and create drafts.

- Trust score: 33/100 (low)
- Change this week: −41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `crimp.studio`: 33/100 (this document), [markdown](https://verifymcp.io/servers/studio-crimp-crimp/api-mcp.md), [page](https://verifymcp.io/servers/studio-crimp-crimp/api-mcp)

## Channel facts

- Endpoint: `https://crimp.studio/api/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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

## Install

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

### Claude

```bash
claude mcp add --transport http studio-crimp-crimp 'https://crimp.studio/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "studio-crimp-crimp": {
      "url": "https://crimp.studio/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "studio-crimp-crimp": {
      "type": "http",
      "url": "https://crimp.studio/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.studio-crimp-crimp]
url = "https://crimp.studio/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "studio-crimp-crimp": {
      "type": "remote",
      "url": "https://crimp.studio/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add studio-crimp-crimp --url 'https://crimp.studio/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  studio-crimp-crimp:
    url: "https://crimp.studio/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "studio-crimp-crimp": {
      "Transport": "http",
      "Url": "https://crimp.studio/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add studio-crimp-crimp -t streamable-http -u 'https://crimp.studio/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "studio-crimp-crimp": {
      "type": "http",
      "url": "https://crimp.studio/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 33, −41)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.53 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Authorization: partial → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-28 (score 74, +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.

### 2026-10-26 (score 73, +1)

- [cosmetic] “create_draft” added an optional parameter “designProfileId”

### 2026-10-23 (score 72, +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.

### 2026-10-21 (score 71, +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.

### 2026-10-19 (score 70, +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.

### 2026-10-17 (score 69, +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.

### 2026-10-15 (score 68, +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.

## MCP tools (5)

### `search_components` (~76 tokens)

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.

Input parameters:

- `category` (string)
- `limit` (integer)
- `offset` (integer)
- `query` (string)

Output parameters:

- `data`
- `error` (object)
- `metadata` (object)
- `ok` (boolean)
- `tool` (string)

### `get_component` (~45 tokens)

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.

Input parameters:

- `catalogId` (string, required)

Output parameters:

- `data`
- `error` (object)
- `metadata` (object)
- `ok` (boolean)
- `tool` (string)

### `calculate_circuit` (~92 tokens)

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.

Input parameters:

- `input` (required)
- `kind` (string, required)
- `units` (string)

Output parameters:

- `data`
- `error` (object)
- `metadata` (object)
- `ok` (boolean)
- `tool` (string)

### `analyze_system` (~95 tokens)

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.

Input parameters:

- `autoSizeTargetPct`
- `system` (object, required)

Output parameters:

- `data`
- `error` (object)
- `metadata` (object)
- `ok` (boolean)
- `tool` (string)

### `create_draft` (~151 tokens)

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.

Input parameters:

- `designProfileId` (string)
- `draft` (object, required)

Output parameters:

- `data`
- `error` (object)
- `metadata` (object)
- `ok` (boolean)
- `tool` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/studio-crimp-crimp/api-mcp#diagnostics

## Score history

- 2026-11-04: 33
- 2026-11-03: 33
- 2026-11-02: 33
- 2026-11-01: 33
- 2026-10-31: 33
- 2026-10-30: 33
- 2026-10-29: 33
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 66

## Common questions

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

## Links

- Remote endpoint: https://crimp.studio/api/mcp
- Website: https://crimp.studio/developers/
- Changelog RSS feed: https://verifymcp.io/servers/studio-crimp-crimp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/studio-crimp-crimp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/studio-crimp-crimp/api-mcp