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

whobuildsit

https://whobuildsit.com

Registry code: e835dfea9d3c8f8d

api record

Search space and defence hardware and the companies that make it, by specification.

Use search_parts for a part or a spec ("3000 psi valve", "heat pipe", "titanium"); numbers with units are

endpoint
https://whobuildsit.com/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 whobuildsit live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is whobuildsit free to use?
Yes — the hub reached it with no key and no payment.
What tools does whobuildsit have?
7 tools: search_parts, request_quote, get_supplier, get_part, search_suppliers, list_categories, explain_standard.
Is whobuildsit 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
356ms

last good check

priced tools
0

of 7 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 7 tools
3 open 4 never probed 3 of 7 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.

  • search_suppliers open 1h ago

    Find companies that can make something — by process (e.g. "5-axis machining", "vacuum brazing"), material, certification (e.g. "AS9100D"), category, or country. Most space hardware is made to drawing by contract manufacturers that have no product catalogue; this is how to find them.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Free text over name, description, capabilities and categories"
        },
        "country": {
          "type": "string",
          "description": "e.g. \"India\", \"United Kingdom\", \"USA\""
        },
        "certification": {
          "type": "string",
          "description": "e.g. \"AS9100D\", \"NADCAP\", \"ISO 9001\""
        }
      }
    }
    arguments 23 lines
  • list_categories open 1h ago

    The part tree (segment → assembly → component) with supplier counts. Use to see what the index covers and where it has gaps.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • explain_standard open 1h ago

    What a standard (AS9100D, NADCAP, ECSS, ISO 9001, MIL-STD …) certifies, why a buyer cares, what it is typically required for, and which suppliers in the index claim it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "standard"
      ],
      "properties": {
        "standard": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • search_parts unknown never probed

    Find parts by keyword and/or numeric specification. Units are understood: "3000 psi" also matches parts rated in bar; "Ø40 mm", "1250 °C", "10 GHz" work. Returns matching parts with supplier, key specs and a URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "e.g. \"3000 psi needle valve\", \"space heat pipe\", \"vacuum furnace 1250 C\""
        },
        "confirmed_only": {
          "type": "boolean",
          "description": "Only parts whose data the manufacturer confirmed"
        }
      }
    }
    arguments 22 lines
  • request_quote unknown never probed

    Send a quote request to whobuildsit, which reviews it and passes it to suppliers who can make the part. Before calling, ASK THE USER for their work email and explicit consent to share the request and email with suppliers — never invent an email. Give a part_id or supplier_slug from earlier results when you have one. Suppliers reply to the user directly; nothing is sent automatically.

    mcp-tool

    {
      "type": "object",
      "required": [
        "requirement",
        "buyer_email",
        "consent"
      ],
      "properties": {
        "nda": {
          "type": "boolean",
          "description": "true if the user will only share drawings after suppliers sign an NDA"
        },
        "consent": {
          "type": "boolean",
          "description": "true only if the user explicitly agreed to share this request and their email with suppliers"
        },
        "part_id": {
          "type": "integer"
        },
        "quantity": {
          "type": "string"
        },
        "needed_by": {
          "type": "string",
          "description": "Date or lead time"
        },
        "buyer_name": {
          "type": "string"
        },
        "buyer_email": {
          "type": "string",
          "description": "The user's work email, as they gave it"
        },
        "requirement": {
          "type": "string",
          "description": "What is needed: part, specification, material, tolerance, certification, drawings available"
        },
        "buyer_company": {
          "type": "string"
        },
        "buyer_country": {
          "type": "string"
        },
        "supplier_slug": {
          "type": "string"
        },
        "export_controlled": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "ITAR/EAR or similar"
        }
      }
    }
    arguments 57 lines
  • get_supplier unknown never probed

    Full profile: what they make, capabilities (process, tolerance, envelope, material, lead time), certifications claimed, categories and products. Contact details are not returned — use the profile URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Supplier slug from a search result"
        }
      }
    }
    arguments 12 lines
  • get_part unknown never probed

    All specifications for one part, whether the manufacturer confirmed them, and the supplier.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "description": "Part id from a search result"
        }
      }
    }
    arguments 12 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 e835dfea9d3c8f8d.

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