Hackshop MCP server

Which servers in the official MCP registry are Hackshop's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to Hackshop

Whose server it is

Registry namedev.hackshop/hackshop-mcpverified in the MCP registry

The registry name sits under hackshop.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-15

Stateanswerschecked 2026-10-15
Tools10
Server calls itselfhackshop
Server version0.0.7
Protocol version2025-06-18

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 197 ms.

Tools it offers10 tools · read 2026-10-15

intake_gadget
Return the 4 intake questions (where it lives, how you interact, room sensing, budget), why each matters and how each answer maps to plan_gadget. Ask the human these, then call plan_gadget with `answers`. No input.
plan_gadget
Deterministically plan a physical body for an AI agent using Meta Muse boards. Ask the intake questions first (intake_gadget, or the `questions` this returns until `intake.complete` is true), then pass the human's choices as `answers`…
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…
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.
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…
find_firmware_playbooks
Find curated owner-authorized firmware, local-protocol and cloud-replacement playbooks. Results prefer the least-invasive path and are not compatibility approval; call check_firmware_compatibility before preparation.
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.
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.
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.
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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Also shipped through: npm

OpenAPI spec

1 paths, read 2026-10-15. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.