83trust / 100

hackshop

by hackshop.dev in Other

MCP serverPassing, checked 4 h ago

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

https://www.hackshop.dev/mcp
Tools
10
open to any client
Uptime
100%
last 30 days
Response time
275 ms
605 ms slowest 5%
Last check
Passed
4 h ago, next in 2 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "hackshop": {
      "type": "http",
      "url": "https://www.hackshop.dev/mcp"
    }
  }
}

10 tools

  • 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…

  • 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…

  • 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…

  • 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.

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
4 h agoPassed200326 ms
15 h agoPassed200278 ms
26 h agoPassed200251 ms
36 h agoPassed200302 ms
46 h agoPassed200325 ms
Show 10 older checks
2 days agoPassed200270 ms
3 days agoPassed200605 ms
3 days agoPassed200258 ms
4 days agoPassed200281 ms
4 days agoPassed200264 ms
4 days agoPassed200229 ms
5 days agoPassed200241 ms
5 days agoPassed200238 ms
6 days agoPassed200412 ms
6 days agoPassed200275 ms