_ registry / mcp streamable-http · checked 19m ago

hackshop

https://www.hackshop.dev

Registry code: f1e5a75d33204208

api record

hackshop maps a project idea to hardware and build steps. Use find_reverse_engineering_examples for curated real-world examples and research methods; evidence labels distinguish repeatable work from author demos and do not imply compatibility. For firmware reuse, call find_firmware_playbooks, then check_firmware_compatibility with exact observed identifiers; destructive actions are human-run only. For a Muse agent body, ask the human the intake questions from intake_gadget, then call plan_gadget with their answers; it is deterministic, instant and key-free. Use get_build_plan for the flash…

endpoint
https://www.hackshop.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is hackshop live?
Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
Is hackshop free to use?
Yes — the hub reached it with no key and no payment.
What tools does hackshop have?
10 tools: check_firmware_compatibility, plan_gadget, get_firmware_playbook, find_firmware_playbooks, assess_hackability, prepare_firmware_job, verify_firmware_artifact, get_build_plan, ….
Is hackshop safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
527ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 270 checks · signed record
  • unknown → live
_ what it is for
used for
  • plan hardware for a gadget project
  • get a device build plan and parts list
  • assess device hackability
takes → gives
text, data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
2 open 8 never probed 2 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_reverse_engineering_examples open 19m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "default": "",
          "maxLength": 2000,
          "description": "Optional case-insensitive search across title, device, exact models, summary, outcome and tags. Empty returns the latest examples."
        },
        "method": {
          "enum": [
            "root",
            "firmware",
            "protocol",
            "app_api",
            "hardware_bus",
            "repurpose",
            "analysis_tool"
          ],
          "type": "string"
        },
        "category": {
          "enum": [
            "display",
            "speaker",
            "input",
            "sensor",
            "bulb",
            "sbc",
            "handheld",
            "mini-pc",
            "wearable",
            "router",
            "other"
          ],
          "type": "string"
        },
        "evidence": {
          "enum": [
            "reproduced",
            "documented",
            "author_demo",
            "analysis_method"
          ],
          "type": "string"
        },
        "use_case": {
          "enum": [
            "calendar",
            "ai_interface",
            "info_panel",
            "smart_home",
            "art"
          ],
          "type": "string",
          "description": "Filter source-backed design starters by intended use."
        },
        "max_device_price_usd": {
          "type": "number",
          "description": "Maximum lowest-listed device price in USD; unknown prices excluded. Accessories, host, shipping and tax are extra; availability is returned separately.",
          "exclusiveMinimum": 0
        }
      }
    }
    arguments 70 lines
  • intake_gadget reads open 19m ago

    Return four hardware-planning intake questions covering placement, interaction, room sensing and budget, with answer options and their planning meanings. No input.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • check_firmware_compatibility unknown 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playbook_id",
        "observed"
      ],
      "properties": {
        "observed": {
          "type": "object",
          "properties": {
            "soc": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Confirmed SoC or module identifier."
            },
            "sensor": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Confirmed image sensor or other sensor identifier."
            },
            "codename": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Documented hardware codename, when available."
            },
            "wifi_module": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Confirmed Wi-Fi or radio module identifier."
            },
            "model_number": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Model number from the physical label, not the retail family name."
            },
            "firmware_version": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Installed vendor firmware version."
            },
            "hardware_revision": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Exact hardware or PCB revision."
            }
          },
          "additionalProperties": false
        },
        "playbook_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        }
      }
    }
    arguments 62 lines
  • plan_gadget reads unknown 19m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "idea": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 3,
          "description": "Gadget idea or use case, 3-2000 characters. Optional when `answers` or `needs` are given."
        },
        "size": {
          "enum": [
            "pocket",
            "desk",
            "wall",
            "hidden",
            "any"
          ],
          "type": "string",
          "default": "any",
          "description": "Preferred size or placement: pocket, desk, wall, hidden, any. Default any."
        },
        "limit": {
          "type": "number",
          "default": 3,
          "maximum": 5,
          "minimum": 1,
          "description": "Number of picks to return: 1-5, default 3."
        },
        "needs": {
          "type": "array",
          "items": {
            "enum": [
              "voice",
              "screen",
              "images",
              "touch",
              "camera",
              "air-sensors",
              "e-ink",
              "battery",
              "round",
              "home-tunnel",
              "big-screen",
              "compute",
              "linux"
            ],
            "type": "string"
          },
          "description": "Optional explicit needs. Allowed: voice, screen, images, touch, camera, air-sensors, e-ink, battery, round, home-tunnel, big-screen, compute, linux."
        },
        "answers": {
          "type": "object",
          "properties": {
            "size": {
              "enum": [
                "pocket",
                "desk",
                "wall",
                "hidden"
              ],
              "type": "string",
              "description": "Where should this body live? pocket = Pocket; desk = Desk; wall = Wall or fridge; hidden = Hidden, no screen."
            },
            "budget": {
              "enum": [
                "under-25",
                "under-50",
                "under-100",
                "no-limit"
              ],
              "type": "string",
              "description": "What budget should I plan around? under-25 = Under $25; under-50 = Under $50; under-100 = Under $100; no-limit = No limit."
            },
            "sensing": {
              "enum": [
                "camera",
                "air-quality",
                "none"
              ],
              "type": "string",
              "description": "Should it sense the room? camera = Camera; air-quality = Air quality; none = None."
            },
            "interaction": {
              "enum": [
                "voice",
                "touch",
                "light-button"
              ],
              "type": "string",
              "description": "How should you interact with it? voice = Talk to it; touch = Touch screen; light-button = Light and button."
            }
          },
          "description": "The human's intake answers, by question id, using the option values from intake_gadget.",
          "additionalProperties": false
        },
        "platform": {
          "enum": [
            "muse-esp32",
            "muse-linux",
            "any"
          ],
          "type": "string",
          "default": "any",
          "description": "Platform filter: muse-esp32, muse-linux, or any. Default any."
        },
        "budget_usd": {
          "type": "number",
          "maximum": 100000,
          "description": "Optional hardware budget in USD. Must be greater than 0, max 100000.",
          "exclusiveMinimum": 0
        },
        "owned_device_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 50,
          "description": "Catalog device ids the user already owns. Max 50."
        }
      }
    }
    arguments 121 lines
  • get_firmware_playbook unknown never probed

    Return a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playbook_id"
      ],
      "properties": {
        "playbook_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        }
      }
    }
    arguments 13 lines
  • find_firmware_playbooks unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "default": 5,
          "maximum": 10,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1
        },
        "device_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "intervention": {
          "enum": [
            "official_local_api",
            "protocol_replacement",
            "cloud_replacement",
            "stock_firmware_overlay",
            "custom_userspace",
            "full_replacement",
            "research_only"
          ],
          "type": "string"
        },
        "risk_tolerance": {
          "enum": [
            "low",
            "moderate",
            "high"
          ],
          "type": "string",
          "default": "moderate"
        }
      }
    }
    arguments 45 lines
  • assess_hackability reads unknown 18h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "device_name"
      ],
      "properties": {
        "device_name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Device name or id, 1-200 characters."
        }
      }
    }
    arguments 14 lines
  • prepare_firmware_job unknown 18h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playbook_id",
        "owner_authorized",
        "observed"
      ],
      "properties": {
        "observed": {
          "type": "object",
          "properties": {
            "soc": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Confirmed SoC or module identifier."
            },
            "sensor": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Confirmed image sensor or other sensor identifier."
            },
            "codename": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Documented hardware codename, when available."
            },
            "wifi_module": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Confirmed Wi-Fi or radio module identifier."
            },
            "model_number": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Model number from the physical label, not the retail family name."
            },
            "firmware_version": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Installed vendor firmware version."
            },
            "hardware_revision": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Exact hardware or PCB revision."
            }
          },
          "additionalProperties": false
        },
        "playbook_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "owner_authorized": {
          "type": "boolean"
        }
      }
    }
    arguments 66 lines
  • verify_firmware_artifact unknown 18h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "playbook_id",
        "filename",
        "sha256",
        "source_url"
      ],
      "properties": {
        "sha256": {
          "type": "string",
          "pattern": "^[a-fA-F0-9]{64}$"
        },
        "filename": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1
        },
        "source_url": {
          "type": "string",
          "format": "uri"
        },
        "playbook_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        }
      }
    }
    arguments 29 lines
  • get_build_plan reads unknown 9h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "device_id"
      ],
      "properties": {
        "device_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Catalog device id, 1-200 characters."
        }
      }
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f1e5a75d33204208.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f1e5a75d33204208/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f1e5a75d33204208/badge.svg)](https://brick.blue/agent/f1e5a75d33204208?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.