hackshop

by hackshop.dev MCP server, indexed and not reviewed

HostedLocalvendor's own

Not reviewed

No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.

How the index works

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

What the official MCP registry says

Facts

MCP registry
dev.hackshop/hackshop-mcp · 0.0.6
Endpoint
https://www.hackshop.dev/mcp
Packages
npm hackshop-mcp stdio
npm / week
75
Registry entry
updated 4 Oct 2026

From the official MCP registry, the package registries and our own checks. JSON · Markdown

Why it's listed

  • It's published in the registry under hackshop.dev, a namespace the registry only gives to whoever proves they control that domain.

Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.

Tools it lists 10 · about 3,136 tokens of context · checked 18 hours ago

ToolWhat it doesHint
intake_gadgetGet the intake questionsReturn four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.read-only
plan_gadgetPlan a Muse gadgetDeterministically 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…read-only
get_build_planGet a 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 purchase policy, steps, machine-readable…read-only
assess_hackabilityAssess 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 support. Input: `device_name` 1-200 chars.read-only
find_reverse_engineering_examplesFind reverse-engineering examplesSearch 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,…read-only
find_firmware_playbooksFind firmware playbooksFind 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.read-only
check_firmware_compatibilityCheck firmware compatibilityFail-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…read-only
get_firmware_playbookGet a firmware playbookReturn a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.read-only
verify_firmware_artifactVerify firmware artifact metadataCompare 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.read-only
prepare_firmware_jobPrepare a firmware job manifestPrepare 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.read-only

What https://www.hackshop.dev/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.

How its tools read to an agent 0 errors · 6 warnings · 0 notes

  • warnTC11check_firmware_compatibilitynone of its 2 parameters has a description
  • warnTC11find_firmware_playbooksnone of its 5 parameters has a description
  • warnTC11find_reverse_engineering_examples4 parameters without a description: category, evidence, limit, method
  • warnTC11get_firmware_playbookits one parameter, playbook_id, has no description
  • warnTC11prepare_firmware_jobnone of its 3 parameters has a description
  • warnTC11verify_firmware_artifactnone of its 4 parameters has a description

The checks from /check and anchor check, run each day on the list above: about 3,136 tokens of definitions. Not part of the score yet. Check your own server.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.