Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

whobuildsit — space & defence hardware suppliers

REMOTE · WHOBUILDSIT.COM

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

Available components

+3 this week 68 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 857 tokens (~122/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://whobuildsit.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=whobuildsit.com CN=YE1,O=Let's Encrypt,C=US 15 Sept 2026 14 Dec 2026 ECDSA 256 ECDSA-SHA384 65ae585583f0e360565ec49c21f83663064
SANs: *.whobuildsit.com, whobuildsit.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of whobuildsit.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
whobuildsit.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://whobuildsit.com/mcp Verified 200
http (plaintext) http://whobuildsit.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~695 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_standard ~64

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.

NameTypeReqDescription
standardstringyes–

No output schema declared.

No examples provided.

get_part ~37

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

NameTypeReqDescription
idintegeryesPart id from a search result

No output schema declared.

No examples provided.

get_supplier ~59

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.

NameTypeReqDescription
slugstringyesSupplier slug from a search result

No output schema declared.

No examples provided.

list_categories ~35

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_quote ~243

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.

NameTypeReqDescription
buyer_companystring––
buyer_countrystring––
buyer_emailstringyesThe user's work email, as they gave it
buyer_namestring––
consentbooleanyestrue only if the user explicitly agreed to share this request and their email with suppliers
export_controlledstring–ITAR/EAR or similar
ndaboolean–true if the user will only share drawings after suppliers sign an NDA
needed_bystring–Date or lead time
part_idinteger––
quantitystring––
requirementstringyesWhat is needed: part, specification, material, tolerance, certification, drawings available
supplier_slugstring––

No output schema declared.

No examples provided.

search_parts ~114

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.

NameTypeReqDescription
confirmed_onlyboolean–Only parts whose data the manufacturer confirmed
limitinteger––
querystringyese.g. "3000 psi needle valve", "space heat pipe", "vacuum furnace 1250 C"

No output schema declared.

No examples provided.

search_suppliers ~143

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.

NameTypeReqDescription
certificationstring–e.g. "AS9100D", "NADCAP", "ISO 9001"
countrystring–e.g. "India", "United Kingdom", "USA"
limitinteger––
querystring–Free text over name, description, capabilities and categories

No output schema declared.

No examples provided.

Install

How do I install the whobuildsit — space & defence hardware suppliers MCP server?

whobuildsit — space & defence hardware suppliers is a hosted endpoint at https://whobuildsit.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · whobuildsit.com

# add to Claude Code
claude mcp add --transport http com-whobuildsit-catalog 'https://whobuildsit.com/mcp'
Common questions

What is the whobuildsit — space & defence hardware suppliers MCP server?

whobuildsit — space & defence hardware suppliers is an MCP server listed in the public MCP registry as com.whobuildsit/catalog. Find space and defence hardware suppliers and parts by specification, process and certification. This page covers its hosted endpoint (https://whobuildsit.com/mcp).

Is the whobuildsit — space & defence hardware suppliers MCP server safe to use?

whobuildsit — space & defence hardware suppliers scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the whobuildsit — space & defence hardware suppliers MCP server expose?

whobuildsit — space & defence hardware suppliers exposes 7 tools: search_parts, search_suppliers, get_supplier, get_part, explain_standard, and 2 more. Their descriptions and schemas cost roughly 695 tokens of context every time the server is loaded.

Does the whobuildsit — space & defence hardware suppliers MCP server require authentication?

No. We connected to whobuildsit — space & defence hardware suppliers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the whobuildsit — space & defence hardware suppliers MCP server still maintained?

whobuildsit — space & defence hardware suppliers is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.