# hackshop (remote · www.hackshop.dev)

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

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

## Components

- remote · `www.hackshop.dev`: 87/100 (this document), [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, [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

- Endpoint: `https://www.hackshop.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.6`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1573 tokens (~104/item across 15 items; 10 tools + 5 resources), lean.
  - 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**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 41% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 is a hosted endpoint at https://www.hackshop.dev/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 dev-hackshop-hackshop-mcp 'https://www.hackshop.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-hackshop-hackshop-mcp": {
      "url": "https://www.hackshop.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-hackshop-hackshop-mcp": {
      "type": "http",
      "url": "https://www.hackshop.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-hackshop-hackshop-mcp]
url = "https://www.hackshop.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-hackshop-hackshop-mcp": {
      "type": "remote",
      "url": "https://www.hackshop.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-hackshop-hackshop-mcp --url 'https://www.hackshop.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-hackshop-hackshop-mcp:
    url: "https://www.hackshop.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-hackshop-hackshop-mcp": {
      "Transport": "http",
      "Url": "https://www.hackshop.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-hackshop-hackshop-mcp -t streamable-http -u 'https://www.hackshop.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-hackshop-hackshop-mcp": {
      "type": "http",
      "url": "https://www.hackshop.dev/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-11-03 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 87, +1)

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

### 2026-10-31 (score 86, +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 85, +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-28 (score 84, +7)

- [security improvement] Authorization: unverified → partial
- [security] Tool “intake_gadget” rewrote its description, which is the text the model reads
- [security] Tool “find_firmware_playbooks” rewrote its description, which is the text the model reads
- [security] Tool “plan_gadget” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: fail → pass

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

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

### 2026-10-24 (score 76, +1)

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

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

### `intake_gadget` (~37 tokens)

Get the intake questions

Return four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.

### `plan_gadget` (~445 tokens)

Plan a Muse gadget

Deterministically plan a physical body for an AI agent using Meta Muse boards. Partial intake answers produce remaining questions and an intake completion status. Inputs: `idea` 3-2000 chars (optional when `answers` or `needs` are given); `answers` {size, interaction, sensing, budget} using the intake option values; `platform` one of muse-esp32, muse-linux, any (default any); `budget_usd` number greater than 0, 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). Boards that meet the hard needs and the budget rank first, cheapest first. Returns fit, notes, warnings, intake status, questions, picks with difficulty, terms and next steps.

Input parameters:

- `answers` (object): The human's intake answers, by question id, using the option values from intake_gadget.
- `budget_usd` (number): Optional hardware budget in USD. Must be greater than 0, max 100000.
- `idea` (string): Gadget idea or use case, 3-2000 characters. Optional when `answers` or `needs` are given.
- `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` (~93 tokens)

Get a build plan

Return the complete deterministic build plan for a catalog device id: difficulty, board-specific flash warnings, parts, shopping list with buy_options, prices checked date and purchase policy, steps, machine-readable assembly with verify checks, 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` (~77 tokens)

Assess hackability

Look up a device by id, exact name or substring and return hackability, brick risk, firmware links, curated firmware playbooks, 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.

### `find_reverse_engineering_examples` (~173 tokens)

Find reverse-engineering examples

Search Hackshop's curated hardware reverse-engineering examples and research methods. With no query, returns the newest dated examples first. Evidence labels distinguish reproduced work, documented implementations, author demos and analysis methods; they do not imply compatibility with similar-looking hardware.

Input parameters:

- `category` (string)
- `evidence` (string)
- `limit` (number)
- `max_device_price_usd` (number): Maximum lowest-listed device price in USD; unknown prices excluded. Accessories, host, shipping and tax are extra; availability is returned separately.
- `method` (string)
- `query` (string): Optional case-insensitive search across title, device, exact models, summary, outcome and tags. Empty returns the latest examples.
- `use_case` (string): Filter source-backed design starters by intended use.

### `find_firmware_playbooks` (~82 tokens)

Find firmware playbooks

Find curated owner-authorized firmware, local-protocol and cloud-replacement playbooks. Results rank less-invasive paths first and contain research guidance rather than device compatibility approval.

Input parameters:

- `device_id` (string)
- `intervention` (string)
- `limit` (number)
- `query` (string, required)
- `risk_tolerance` (string)

### `check_firmware_compatibility` (~69 tokens)

Check firmware compatibility

Fail-closed compatibility check for one firmware playbook. Required model, codename, revision, SoC or firmware identifiers must exactly match a curated target; missing facts return unknown and mismatches return unsupported.

Input parameters:

- `observed` (object, required)
- `playbook_id` (string, required)

### `get_firmware_playbook` (~52 tokens)

Get a firmware playbook

Return a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.

Input parameters:

- `playbook_id` (string, required)

### `verify_firmware_artifact` (~81 tokens)

Verify firmware artifact metadata

Compare a caller-supplied filename, source URL and SHA-256 with Hackshop's curated metadata. Hackshop does not fetch, upload or redistribute the artifact; absent hashes return unknown.

Input parameters:

- `filename` (string, required)
- `playbook_id` (string, required)
- `sha256` (string, required)
- `source_url` (string, required)

### `prepare_firmware_job` (~70 tokens)

Prepare a firmware job manifest

Prepare a non-executing firmware manifest after owner authorization and an exact compatibility match. Returns backup, recovery, sources, validation and stop points; never returns a flash command.

Input parameters:

- `observed` (object, required)
- `owner_authorized` (boolean, required)
- `playbook_id` (string, required)

## Diagnostics

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

## Score history

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

## 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 hosted endpoint (https://www.hackshop.dev/mcp).

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

hackshop scores 87 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 hackshop MCP server expose?

hackshop exposes 10 tools: intake_gadget, plan_gadget, get_build_plan, assess_hackability, find_reverse_engineering_examples, and 5 more. Their descriptions and schemas cost roughly 1,179 tokens of context every time the server is loaded.

### Does the hackshop MCP server require authentication?

No. We connected to hackshop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

## Links

- Remote endpoint: https://www.hackshop.dev/mcp
- Website: https://www.hackshop.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/www.json
- HTML version of this page: https://verifymcp.io/servers/dev-hackshop-hackshop-mcp/www