Connect-MCP

hackshop

dev.hackshop/hackshop-mcp · v0.0.6

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

MCPremotelocal · npmno credentials

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 10 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 89/100

What it does: 10 tools · 6 read, 0 write

Test call find_reverse_engineering_examples: worked (1,084 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +4
  • Read/write annotations: 0
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://www.hackshop.dev/mcp
Package
registry:   npm
identifier: hackshop-mcp
version:    0.0.6
transport:  stdio

Tools

10 tools listed at last check
  • 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.

Badge

Connect-MCP badge for dev.hackshop/hackshop-mcp

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/dev.hackshop/hackshop-mcp.svg)](https://clawy.uk/mcp/s/dev.hackshop/hackshop-mcp)

Website