hackshop
REMOTE · WWW.HACKSHOP.DEV · 2 COMPONENTS
Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing.
Available components
Last scanned (8 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1573 tokens (~104/item across 15 items; 10 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 41% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +7
- Authorization: unverified → partial ▲ security
- Tool “intake_gadget” rewrote its description, which is the text the model reads security
- Tool “find_firmware_playbooks” rewrote its description, which is the text the model reads security
- Tool “plan_gadget” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.hackshop.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.hackshop.dev | CN=YR1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | RSA 2048 | SHA256-RSA | 6f60b109f6c0cb71ce742219b726bc8ff97 |
| SANs: *.hackshop.dev, hackshop.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.hackshop.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| hackshop.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.hackshop.dev/mcp | Verified | 200 | |
| http (plaintext) | http://www.hackshop.dev/mcp | HTTPS enforced | 308 | https://www.hackshop.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_hackability Assess hackability ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_name | string | yes | Device name or id, 1-200 characters. |
Structured output declared, but exposes no named fields.
No examples provided.
check_firmware_compatibility Check firmware compatibility ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| observed | object | yes | – |
| playbook_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_firmware_playbooks Find firmware playbooks ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | – |
| intervention | string | – | – |
| limit | number | – | – |
| query | string | yes | – |
| risk_tolerance | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_reverse_engineering_examples Find reverse-engineering examples ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| evidence | string | – | – |
| limit | number | – | – |
| max_device_price_usd | number | – | Maximum lowest-listed device price in USD; unknown prices excluded. Accessories, host, shipping and tax are extra; availability is returned separately. |
| method | string | – | – |
| query | string | – | Optional case-insensitive search across title, device, exact models, summary, outcome and tags. Empty returns the latest examples. |
| use_case | string | – | Filter source-backed design starters by intended use. |
Structured output declared, but exposes no named fields.
No examples provided.
get_build_plan Get a build plan ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | yes | Catalog device id, 1-200 characters. |
Structured output declared, but exposes no named fields.
No examples provided.
get_firmware_playbook Get a firmware playbook ~52
Return a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| playbook_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
intake_gadget Get the intake questions ~37
Return four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
plan_gadget Plan a Muse gadget ~445
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | The human's intake answers, by question id, using the option values from intake_gadget. |
| budget_usd | number | – | Optional hardware budget in USD. Must be greater than 0, max 100000. |
| idea | string | – | Gadget idea or use case, 3-2000 characters. Optional when `answers` or `needs` are given. |
| limit | number | – | Number of picks to return: 1-5, default 3. |
| needs | array | – | Optional explicit needs. Allowed: voice, screen, images, touch, camera, air-sensors, e-ink, battery, round, home-tunnel, big-screen, compute, linux. |
| owned_device_ids | array | – | Catalog device ids the user already owns. Max 50. |
| platform | string | – | Platform filter: muse-esp32, muse-linux, or any. Default any. |
| size | string | – | Preferred size or placement: pocket, desk, wall, hidden, any. Default any. |
Structured output declared, but exposes no named fields.
No examples provided.
prepare_firmware_job Prepare a firmware job manifest ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| observed | object | yes | – |
| owner_authorized | boolean | yes | – |
| playbook_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_firmware_artifact Verify firmware artifact metadata ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | – |
| playbook_id | string | yes | – |
| sha256 | string | yes | – |
| source_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the hackshop MCP server?
hackshop is a hosted endpoint at https://www.hackshop.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.hackshop.dev
claude mcp add --transport http dev-hackshop-hackshop-mcp 'https://www.hackshop.dev/mcp'
What is the hackshop MCP server?
hackshop is an MCP server listed in the public MCP registry as dev.hackshop/hackshop-mcp. Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing. This page covers its hosted endpoint (https://www.hackshop.dev/mcp).
Is the hackshop MCP server safe to use?
hackshop scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the hackshop MCP server expose?
hackshop exposes 10 tools: intake_gadget, plan_gadget, get_build_plan, assess_hackability, find_reverse_engineering_examples, and 5 more. Their descriptions and schemas cost roughly 1,179 tokens of context every time the server is loaded.
Does the hackshop MCP server require authentication?
No. We connected to hackshop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the hackshop MCP server still maintained?
hackshop is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.