# hackshop

- Registry name: `dev.hackshop/hackshop-mcp` · version 0.0.6
- Categories (automatic, keyword rules): Research & knowledge, Search & data, Shops & products, Commerce & marketing, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.hackshop%2Fhackshop-mcp
- Server page: https://mcpstation.net/s/dev.hackshop--hackshop-mcp.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://www.hackshop.dev/mcp`

## Tools (as reported by the server, not verified)

- `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\`. Inputs: \`idea\` 3-2000 chars \(optional when \`answers\` or \`needs\`
- `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. Inp
- `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 compatibility with similar-looki
- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html