bots.st/hackshop
hackshop
Plan boards, parts, assembly and pairing
1983 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 10
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://www.hackshop.dev/mcp - npm
npx -y hackshop-mcpReleased 4 Oct 2026, version 0.0.6
What it can do
| Tool | What it says it does |
|---|---|
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. |
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. |
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… |
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… |
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. |
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, budget} using the… |
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. |
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. |
In its maker's words
Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing.
- Website
- www.hackshop.dev
- Publisher
- hackshop.dev
- Listed from
- the official MCP Registry as
dev.hackshop/hackshop-mcp - Version
- 0.0.6, updated 4 Oct 2026
- Kinds of work
- Devices and the physical world, Documents and files, Security and trust
The domain it lives on
- hackshop.dev
- registered 5 May 2026 (6 months ago), at Name.com, Inc, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1983 ms | |
| Answered | 2127 ms | |
| Answered | 688 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.