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

hackshop

https://www.hackshop.dev

Registry code: f1e5a75d33204208

api record

Hackshop maps a project idea to hardware and build steps. Use plan_gadget for Muse agent-body gadgets because it is deterministic, instant and key-free. Use get_build_plan for shopping lists, machine-readable assembly and the agent brief, then ask the human before buying anything. Hosted MCP exposes deterministic tools only; propose_hardware and simulate_assembly are npm-only because they can cost money or require external workers. Hackshop never buys anything. Hosted MCP logs tool names and timings only.

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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
179ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • plan_gadget unknown never probed

    Deterministically plan a physical body for an AI agent using Meta Muse boards. Inputs: `idea` 3-2000 chars; `platform` one of muse-esp32, muse-linux, any (default any); `budget_usd` positive number 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). Returns fit, notes, warnings, intake questions, picks, terms and next steps.

    mcp-tool

    {
  "type": "object",
  "required": [
    "idea"
  ],
  "properties": {
    "idea": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 3,
      "description": "Gadget idea or use case, 3-2000 characters."
    },
    "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."
    },
    "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 79 lines
  • get_build_plan unknown 19h ago

    Return the complete deterministic build plan for a catalog device id: parts, shopping list with buy_options and store URLs, steps, machine-readable assembly, 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
  • assess_hackability unknown never probed

    Look up a device by id, exact name or substring and return hackability, brick risk, firmware links, 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
_ 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
70%

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.