Skip to content

hackshop

by hackshop.dev · remote · local (npm) · no sign-in to list tools · v0.0.6 · published by dev.hackshop

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

Changes · 4
CompareRegistry entry

10 tools: 4 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

10 tools

Changes things 4Claude Code: ask
  • assess_hackabilityLook 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 suppor…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_compatibilityFail-closed compatibility check for one firmware playbook.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • plan_gadgetDeterministically plan a physical body for an AI agent using Meta Muse boards.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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` 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.
  • prepare_firmware_jobPrepare a non-executing firmware manifest after owner authorization and an exact compatibility match.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 6Claude Code: allow
  • find_firmware_playbooksFind curated owner-authorized firmware, local-protocol and cloud-replacement playbooks.No findings

    Why it is in this group

    • The name "find_firmware_playbooks" says "find": a word for reading.
    Description, as the server wrote it
    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.
  • find_reverse_engineering_examplesSearch Hackshop's curated hardware reverse-engineering examples and research methods.No findings

    Why it is in this group

    • The name "find_reverse_engineering_examples" says "find": a word for reading.
    Description, as the server wrote it
    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.
  • get_build_planReturn 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 purc…No findings

    Why it is in this group

    • The name "get_build_plan" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_firmware_playbookReturn a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action bou…No findings

    Why it is in this group

    • The name "get_firmware_playbook" says "get": a word for reading.
    Description, as the server wrote it
    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_gadgetReturn the 4 intake questions (where it lives, how you interact, room sensing, budget), why each matters and how each answer maps to plan_gadget.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.
  • verify_firmware_artifactCompare a caller-supplied filename, source URL and SHA-256 with Hackshop's curated metadata.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.0.6. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hackshop__intake_gadget",
      "mcp__hackshop__get_build_plan",
      "mcp__hackshop__find_reverse_engineering_examples",
      "mcp__hackshop__find_firmware_playbooks",
      "mcp__hackshop__get_firmware_playbook",
      "mcp__hackshop__verify_firmware_artifact"
    ],
    "ask": [
      "mcp__hackshop__plan_gadget",
      "mcp__hackshop__assess_hackability",
      "mcp__hackshop__check_firmware_compatibility",
      "mcp__hackshop__prepare_firmware_job"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as hackshop. Review it before you use it.