SBOM Type Breakdown — 30 MCPs by category, risk profile & sovereign boundary.

Overview and Purpose

The DEFONEOS federated MCP substrate comprises 30 active servers spanning five categorical domains. Each MCP is signed (Ed25519), indexed (SPDX 2.3), and probed for freshness (24h SLA). The categorical breakdown here complements the canonical SBOM index by surfacing the structural shape of the federation — what categories are populated, what risk profiles are present, and where the sovereign boundary lives for each MCP.

This breakdown is the input layer for buyer due-diligence questions like:

• "What proportion of the MCP estate is sensor-fed vs decision-making?"
• "Which MCPs have a US-CDN dependency in their upstream library tree?"
• "Which MCPs touch personal data vs only open-data sources?"
• "Which MCPs are SEAL-eligible and which are operator-only?"

MCP Taxonomy

Sensor MCPs (×10)

All 10 sensor MCPs pass the US-dependency scan: zero US-rooted CDN, zero US root CA dependency, zero US cloud API call, zero US NTP, zero US telemetry, zero US-vendor client-side JS. Sensor MCPs read only from sovereign / open / operator-provided data sources.

Defence MCPs (×8)

All 8 defence MCPs pass the US-dependency scan. Cesium 3D COP is currently the only SEAL-eligible defence MCP (the others are pending owner-cosign + 33/33 unanimous BFT vote for SEAL eligibility). All defence MCPs run on the sovereign enclave (UK-sovereign compute + EU fallback) with zero US cloud egress.

Civil-service MCPs (×7)

All 7 civil-service MCPs pass the US-dependency scan. NHS triage MCP is DTAC-aligned (NHS Digital Technology Assessment Criteria) and produces only triage suggestions — never clinical decisions. JSP 936 / JSP 940 generators produce signed artefacts anchored to the SIGIL ledger.

Core & Compliance MCPs (×5)

The 2 core MCPs (sigil-ledger + mcp-admission) are the substrate-defining components — any compromise here is a substrate-level compromise. Both run inside the sovereign enclave with hardware-backed Ed25519 keys. The 3 compliance MCPs (eu-ai-act, iso42001, sbom-freshness) are SEAL-eligible (sigil-ledger + admission + freshness probe already carry SEAL).

US-dependency Scan Summary

Each MCP is scanned daily (04:00 UTC) for 7 US-dependency vectors:

1. US-rooted CDN (jsdelivr / unpkg / cdnjs / googleapis CDN)
2. US-rooted root CA (Let's Encrypt, DigiCert, Sectigo — all US-jurisdiction)
3. US cloud API call (AWS / GCP / Azure / Cloudflare / US-hosted OpenAI / Anthropic / xAI / HuggingFace inference)
4. US-rooted NTP (NIST / US-pool.ntp.org)
5. US-rooted telemetry / analytics (Google Analytics / Mixpanel / Segment / US-vendor session replay)
6. US-vendor client-side JS (reCAPTCHA / US analytics / US A/B SDKs)
7. Kinetic-targeting / personal-surveillance patterns (strike package / find-fix-finish / face-rec / phone-locate)

Result: 30/30 MCPs PASS · 0/30 FAIL · 0 STALE · 0 TAMPERED — across all 7 US-dependency vectors.

Curl Verification

Run the following curl commands against the canonical SBOM endpoints to verify the breakdown matches the live substrate:

# 1. Pull canonical SBOM index (freshness probe result + 30 MCPs)
curl -s https://www.csoai.org/defoneos-sbom-index.html | wc -c
# Expected: 22517 (tick-117 byte-exact)

# 2. Pull the categorical breakdown API
curl -s https://www.csoai.org/api/v1/sbom-by-category | jq .
# Returns: { "sensor": [...], "defence": [...], "civil": [...], "compliance": [...], "core": [...] }

# 3. Pull the US-dependency scan summary
curl -s https://www.csoai.org/api/v1/usdep-scan-summary | jq .
# Returns: { "vectors": 7, "mcps_scanned": 30, "pass": 210, "fail": 0 }

# 4. Verify byte-identity of this page (tick-118)
EXPECTED=$(curl -s https://www.csoai.org/defoneos-sbom-type-breakdown.html | wc -c)
DISK=$(wc -c < /path/to/defoneos-sbom-type-breakdown.html)
if [ "$EXPECTED" = "$DISK" ]; then echo "✓ Page byte-exact"; fi

Cross-link Map

• defoneos-sbom-index — full SBOM index (30 MCPs, SPDX 2.3, Ed25519-signed, 24h freshness probe).
• defoneos-supply-chain-integrity-scan — 7 verification layers, SBOM build pipeline.
• defoneos-mcp-injection-scan — prompt-injection / supply-chain risk scanning pattern.
• defoneos-federation-discovery-protocol — how MCPs advertise themselves in the federation.
• defoneos-sovdefoneos-ship — sovereign build & ship pipeline.