hackshop MCP Server

by hackshop Your server? Claim it

not responding

hackshop is listed as active in the registry but did not answer our last check. 71 installs a week from npm. It exposes 10 tools.

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

Installs per day peak 327 · avg 20 · +3206% w/w

a month agotoday

Uptime history 36 days of history · worst day 0%

36 days agonow

1.1%

Uptime 24h

1 of 91 checks

Tools

read from the server

250 ms

Response time

average over 24h

Installs / week

npm and PyPI

What changed 14

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 October 2026. No other catalogue keeps this.

27 Oct 3 tool descriptions were rewritten find_firmware_playbooks, intake_gadget, plan_gadget

14 Oct a tool appeared find_reverse_engineering_examples

8 Oct 5 tools appeared check_firmware_compatibility, find_firmware_playbooks, get_firmware_playbook and 2 more

8 Oct a tool description was rewritten assess_hackability

6 Oct 2 tool descriptions were rewritten get_build_plan, plan_gadget

6 Oct a tool appeared intake_gadget

6 Oct a tool changed the parameters it asks for plan_gadget

hackshop does not always answer

Over the last week it answered 6.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add hackshop-mcp --transport http https://www.hackshop.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://www.hackshop.dev/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

firmware

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.

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.

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

assess

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.

build

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

intake

intake_gadget

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

plan

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

prepare

prepare_firmware_job

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.

reverse

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.

verify

verify_firmware_artifact

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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.hackshop.dev/mcp	streamable-http	answering	88 ms	9 min ago

Alternatives to hackshop

same job, measured the same way

Human Mailbox

by humanmailbox

A physical postal address in Germany for AI agents. A human opens, scans and forwards your mail.

32 tools answering

EventAssets

by eventassets

Plan and host your events: event page, guest list, RSVP, seating, agenda, budget and media.

answering

CookNest

by cooknest

Your CookNest recipes in AI chat: find, save and import recipes, plan meals, build shopping lists.

answering

mythOS.vision

by the-reality-engineer

A living memory and world-building layer for your AI: cards, worlds, personas and agent dispatch.

answering

Glongus MCP

by glongusmain

Let your agent buy and sell physical goods, with escrow and shipping.

392 installs/wk answering

Seldonframe

by seldonframe

Build, deploy, and sell AI agents for local-service businesses - from your IDE.

answering

Cor

by getcor

Run customer onboarding from your AI tool: build plans, deploy agents, find bottlenecks.

answering

Agent Board

by easyrider

Classifieds board for AI agents: free search and publishing, x402-paid full listings

3 tools answering

hackshop — questions

Answers built from our own checks of this server.

What can hackshop do?

It exposes 10 tools, read directly from the server on our last check. Among them: assess_hackability, check_firmware_compatibility, find_firmware_playbooks, find_reverse_engineering_examples, get_build_plan, get_firmware_playbook and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is hackshop working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 250 ms. The bar chart above shows every period we have measured.

The registry lists hackshop as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect hackshop?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does hackshop need an API key?

No. hackshop completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is hackshop?

It answers our handshake in 250 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use hackshop?

The npm package hackshop-mcp was installed 71 times in the last week. Week over week that is +3206%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.