hackshop

dev.hackshop/hackshop-mcpVersion 0.0.6

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

Status

Responds222 msNov 14, 2026, 14:26 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:26 UTC
Latency: 222 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://www.hackshop.dev/mcpResponds222 msNov 14, 2026, 14:26 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: hackshop-mcp
Remote MCP server URL: https://www.hackshop.dev/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"hackshop-mcp","type":"http","url":"https://www.hackshop.dev/mcp"}'

Streamable HTTP

npm: hackshop-mcp 0.0.6

Package only

npm (npx)

claude mcp add hackshop-mcp -- npx -y hackshop-mcp@0.0.6

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

10 tools

Tools of hackshop
	Description		Read-only	Idempotent	Open world
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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 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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	Return a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.	No	Yes	Yes	No
`intake_gadget`Return four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.	Return four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No

Details

Registry status: Active
Published: Oct 4, 2026
Updated: Oct 4, 2026
Website: https://www.hackshop.dev/⁠ (opens in a new tab)
Repository: Not given
Categories: Uncategorized
GDPR: Not declared

Are you the operator? Claim this listing