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

protoship

https://mcp.protoship.dev

Registry code: 2dae682f56cb9db1

api record

Protoship builds small USB-powered devices from a standard parts catalog (Arduino Nano ESP32 plus Qwiic and Grove modules: climate, CO2, display, presence, relay, LED ring, servos) and delivers them assembled. Flow: call catalog, pick modules for what your user wants the device to do, call quote for the total incl. shipping and VAT, show the total to your user, then call reserve with their email address once they agree (a budget your user set in advance counts as agreement). A reservation costs nothing and obliges nobody; Protoship emails when the device can be ordered. Each quote includes an…

endpoint
https://mcp.protoship.dev
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 protoship live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is protoship free to use?
Yes — the hub reached it with no key and no payment.
What tools does protoship have?
5 tools: quote, status, reserve, join_waitlist, catalog.
Is protoship 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
73ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
1 open 4 never probed 1 of 5 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.

  • catalog open 1h ago

    Lists the parts a Protoship device is built from: the always-included Arduino Nano ESP32 on its carrier, the modules (function, plug, I2C address, limits) and the enclosure options, plus the power and delivery rules. Free, no side effects.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • quote unknown 1h ago

    Prices a device built from catalog modules: parts, enclosure, assembly, shipping, Protoship fee and VAT for the destination country, as one total, plus a delivery estimate, a quote_id for reserve, a reserve_url your user can open, and an ESPHome starter config. If the device breaks a rule (power, plugs, unknown part), it returns the problems to fix. Free, no side effects.

    mcp-tool

    {
      "type": "object",
      "required": [
        "parts"
      ],
      "properties": {
        "parts": {
          "type": "array",
          "items": {
            "enum": [
              "bme280",
              "scd41",
              "oled",
              "servo_driver",
              "micro_servo",
              "pir",
              "relay",
              "led_ring",
              "micro_servo:2"
            ],
            "type": "string"
          },
          "description": "Module ids from catalog, e.g. [\"bme280\", \"oled\"]. Repeat an id or use \"micro_servo:2\" for two. The Nano ESP32 and the carrier are always included."
        },
        "units": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "How many identical devices. Default 1."
        },
        "country": {
          "type": "string",
          "description": "Two-letter EU country code of the delivery address, e.g. DE. Default DE."
        },
        "enclosure": {
          "enum": [
            "printed",
            "none"
          ],
          "type": "string",
          "description": "printed (default) or none."
        }
      },
      "additionalProperties": false
    }
    arguments 45 lines
  • status unknown 1h ago

    Returns the state of a reservation (pending until the email is confirmed, then confirmed), the device and its total.

    mcp-tool

    {
      "type": "object",
      "required": [
        "reservation_id"
      ],
      "properties": {
        "reservation_id": {
          "type": "string",
          "description": "The id reserve returned, e.g. R-7KQ2M9XW4P."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • reserve unknown never probed

    Reserves the device from a quote for your user. No payment and no obligation to buy. Protoship sends one email to confirm the address and the reservation, and one when the device can be ordered. No newsletter. Use only your user's own email address, only after showing them the total and with their consent. Privacy policy: https://protoship.dev/privacy

    mcp-tool

    {
      "type": "object",
      "required": [
        "quote_id",
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "description": "Your user's email address."
        },
        "purpose": {
          "type": "string",
          "maxLength": 280,
          "description": "What the device is for, in a sentence. Optional."
        },
        "quote_id": {
          "type": "string",
          "description": "quote_id from quote."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • join_waitlist unknown never probed

    Puts your user on the Protoship waitlist, for PCBs, 3D prints, CNC parts, sheet metal or devices outside the catalog. Protoship sends one email to confirm the address, later one with the invite. No newsletter. Use only your user's own email address and only with their consent. Privacy policy: https://protoship.dev/privacy

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "description": "Your user's email address."
        },
        "device": {
          "type": "string",
          "maxLength": 280,
          "description": "The device your user wants to build, in a sentence. Optional."
        },
        "interests": {
          "type": "array",
          "items": {
            "enum": [
              "pcbs",
              "3d_prints",
              "cnc_parts",
              "sheet_metal",
              "assembled_devices",
              "not_sure"
            ],
            "type": "string"
          },
          "description": "What your user wants to order. Optional."
        }
      },
      "additionalProperties": false
    }
    arguments 34 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 2dae682f56cb9db1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2dae682f56cb9db1/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/2dae682f56cb9db1/badge.svg)](https://brick.blue/agent/2dae682f56cb9db1?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
90%

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.