hackshop

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Computer or cloud
• Transport: stdio, Streamable HTTP
• Category: Other
• You need to fill in: ANTHROPIC_API_KEY

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet
• npmNode.js installed (for the npx command)

Which app do you use?

https://www.hackshop.dev/mcp

{
  "mcpServers": {
    "hackshop": {
      "command": "npx",
      "args": [
        "-y",
        "hackshop-mcp"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "HACKSHOP_TELEMETRY": "your-value"
      }
    }
  }
}

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

claude mcp add hackshop --env ANTHROPIC_API_KEY=your-value --env HACKSHOP_TELEMETRY=your-value -- npx -y hackshop-mcp

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

{
  "mcpServers": {
    "hackshop": {
      "command": "npx",
      "args": [
        "-y",
        "hackshop-mcp"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "HACKSHOP_TELEMETRY": "your-value"
      }
    }
  }
}

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

{
  "servers": {
    "hackshop": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "hackshop-mcp"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "HACKSHOP_TELEMETRY": "your-value"
      }
    }
  }
}

https://www.hackshop.dev/mcp

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• ANTHROPIC_API_KEY secret env
  Optional. Improves propose_hardware when the MCP host cannot sample.
• HACKSHOP_TELEMETRY env
  Set to 0 to turn off anonymous usage pings.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.

• 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_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, bu

• 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 ag

• 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 analysis methods; they do not imply compatibilit

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

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (hackshop.dev) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 457 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 10 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 19031 servers in this category
• Published to the registry more recently than 56% of the other 19031 servers in this category
• Basic checks equal to or better than 38% of the other 19031 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo