# hackshop (npm · hackshop-mcp)

Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing.

- Trust score: 74/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.hackshop.dev`: 87/100, [markdown](https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/www.md), [page](https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/www)
- npm · `hackshop-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/hackshop-mcp.md), [page](https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/hackshop-mcp)

## Channel facts

- Registry: `npm`
- Package: `hackshop-mcp`
- Version: `0.0.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 32 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 981 tokens (~122/item across 8 items; 5 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "simulate_assembly" implies "drop" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the hackshop MCP server?

hackshop runs locally as an npm package, launched with npx -y hackshop-mcp. 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 dev-hackshop-hackshop-mcp -- npx -y hackshop-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-hackshop-hackshop-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hackshop-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-hackshop-hackshop-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hackshop-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-hackshop-hackshop-mcp -- npx -y hackshop-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-hackshop-hackshop-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "hackshop-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-hackshop-hackshop-mcp --command npx --arg -y --arg hackshop-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-hackshop-hackshop-mcp:
    command: "npx"
    args: ["-y", "hackshop-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-hackshop-hackshop-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "hackshop-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-hackshop-hackshop-mcp -t stdio -c npx -a -y hackshop-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-hackshop-hackshop-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hackshop-mcp"
      ]
    }
  }
}
```

## 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-11-03 (score 74, +1)

- [security] Stability: 0.97 → pass

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

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 69, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `propose_hardware` (~138 tokens)

Given a project idea (vague is fine), return 3-5 hardware proposals with 'why this fits', hack difficulty, brick risk (with safety rule applied), firmware links, community size, and a suggested eBay search query string. Compose with ebay-mcp at the host level for live listings.

Input parameters:

- `budget_usd` (number): Optional budget in USD. Affects eBay query suggestions.
- `constraints` (string): Optional constraints (e.g., 'must be wall-mountable', 'low power').
- `idea` (string, required): Project idea, free-form. Vague is OK; the agent will use creativity.

### `plan_gadget` (~343 tokens)

Plan a Muse gadget

Deterministically plan a physical body for an AI agent using Meta Muse boards. Inputs: `idea` 3-2000 chars; `platform` one of muse-esp32, muse-linux, any (default any); `budget_usd` positive number up to 100000; `owned_device_ids` up to 50 catalog ids; `needs` values: voice, screen, images, touch, camera, air-sensors, e-ink, battery, round, home-tunnel, big-screen, compute, linux; `size` one of pocket, desk, wall, hidden, any (default any); `limit` 1-5 (default 3). Returns fit, notes, warnings, intake questions, picks, terms and next steps.

Input parameters:

- `budget_usd` (number): Optional hardware budget in USD. Must be greater than 0, max 100000.
- `idea` (string, required): Gadget idea or use case, 3-2000 characters.
- `limit` (number): Number of picks to return: 1-5, default 3.
- `needs` (array): Optional explicit needs. Allowed: voice, screen, images, touch, camera, air-sensors, e-ink, battery, round, home-tunnel, big-screen, compute, linux.
- `owned_device_ids` (array): Catalog device ids the user already owns. Max 50.
- `platform` (string): Platform filter: muse-esp32, muse-linux, or any. Default any.
- `size` (string): Preferred size or placement: pocket, desk, wall, hidden, any. Default any.

### `get_build_plan` (~79 tokens)

Get a build plan

Return the complete deterministic build plan for a catalog device id: parts, shopping list with buy_options and store URLs, steps, machine-readable assembly, commands, links, caveats and an agent-ready brief. Input: `device_id` 1-200 chars.

Input parameters:

- `device_id` (string, required): Catalog device id, 1-200 characters.

### `assess_hackability` (~72 tokens)

Assess hackability

Look up a device by id, exact name or substring and return hackability, brick risk, firmware links, community size, build page and agent platform support. Input: `device_name` 1-200 chars.

Input parameters:

- `device_name` (string, required): Device name or id, 1-200 characters.

### `simulate_assembly` (~180 tokens)

Drop a proposed robot Assembly into a MuJoCo physics world and run a bounded navigation rollout. Returns whether it reached the goal plus honest failure telemetry (stuck/tipped/collisions/heading-oscillation), a natural-language post-mortem, and artifact URLs (rendered mp4, scene.xml, control.py, telemetry.json). Today simulates the diff-drive 'navigate' slice; other goal kinds return an honest 'unsupported'. Requires a configured simulation service.

Input parameters:

- `assembly` (object, required): Assembly IR: { idea, components[{ref,device_id,name,role}], edges[], goal{kind,spec,success_metric}, world{template,goal_xy?} }. Build it with the site /api/assembly output or by hand.
- `duration_s` (number): Optional sim seconds (<=10, bounded). Default 8.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/hackshop-mcp#diagnostics

## Score history

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

## Common questions

### What is the hackshop MCP server?

hackshop is an MCP server listed in the public MCP registry as dev.hackshop/hackshop-mcp. Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing. This page covers its npm package (hackshop-mcp).

### Is the hackshop MCP server safe to use?

hackshop scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 hackshop MCP server expose?

hackshop exposes 5 tools: propose_hardware, plan_gadget, get_build_plan, assess_hackability, simulate_assembly. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.

### Is the hackshop MCP server still maintained?

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

### What licence is the hackshop MCP server under?

hackshop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/hackshop-mcp
- Socket report: https://socket.dev/npm/package/hackshop-mcp
- Website: https://www.hackshop.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/hackshop-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/hackshop-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/hackshop-mcp