whobuildsit — space & defence hardware suppliers

Find space and defence hardware suppliers and parts by specification, process and certification.

Should I use this

Quality & Safety

A
Description quality
94%
Schema completeness
83%
Naming quality
94%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,003Tokens (tool definitions)
~859 BTypical response size
Moderate attention impact (0.78% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "catalog": {
      "url": "https://whobuildsit.com/mcp"
    }
  }
}

Remote endpoints

https://whobuildsit.com/mcpstreamable-http

What it can do

Tool inventory

Tools (7)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_parts(query, confirmed_only, limit)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "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"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 10
    }
  },
  "required": [
    "query"
  ]
}
🟢search_suppliers(query, country, certification, limit)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "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\""
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 10
    }
  }
}
🟢get_supplier(slug)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Supplier slug from a search result"
    }
  },
  "required": [
    "slug"
  ]
}
🟢get_part(id)

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

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "description": "Part id from a search result"
    }
  },
  "required": [
    "id"
  ]
}
🟢explain_standard(standard)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "standard": {
      "type": "string"
    }
  },
  "required": [
    "standard"
  ]
}
🟡request_quote(requirement, quantity, needed_by, part_id, supplier_slug, ...)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "requirement": {
      "type": "string",
      "description": "What is needed: part, specification, material, tolerance, certification, drawings available"
    },
    "quantity": {
      "type": "string"
    },
    "needed_by": {
      "type": "string",
      "description": "Date or lead time"
    },
    "part_id": {
      "type": "integer"
    },
    "supplier_slug": {
      "type": "string"
    },
    "buyer_email": {
      "type": "string",
      "description": "The user's work email, as they gave it"
    },
    "buyer_name": {
      "type": "string"
    },
    "buyer_company": {
      "type": "string"
    },
    "buyer_country": {
      "type": "string"
    },
    "export_controlled": {
      "type": "string",
      "enum": [
        "yes",
        "no",
        "unsure"
      ],
      "description": "ITAR/EAR or similar"
    },
    "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"
    }
  },
  "required": [
    "requirement",
    "buyer_email",
    "consent"
  ]
}
🟢list_categories

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

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded7 tools