30 MCPs in 3 trust rings · inward-cascade data flow · SIGIL per tool invocation · BFT admission control · federation discovery via /.well-known/ manifest.
The DEFONEOS MCP (Model Context Protocol) Federation is a constellation of 30 independent MCP servers, each providing tool capabilities to the sovereign AI inference layer. MCPs are organised into 3 trust rings based on data sensitivity and jurisdictional requirements.
The innermost ring. These MCPs handle governance, compliance, and cryptographic operations. UK-sovereign-only inference — no external API calls whatsoever.
| # | MCP | Function | Trust Level |
|---|---|---|---|
| 1 | sigil-mcp | SIGIL attestation ledger — every tool invocation is signed, timestamped, anchored | Ring 0 |
| 2 | bft-mcp | 33-agent BFT governance council — voting, quorum, session management | Ring 0 |
| 3 | compliance-mcp | JSP 936, GDPR, EU AI Act compliance reporting automation | Ring 0 |
| 4 | seal-mcp | DEFONEOS-SEAL credential issuance — requires 23/33 BFT vote | Ring 0 |
| 5 | redteam-mcp | Adversarial red-team framework — continuous probing, severity classification | Ring 0 |
| 6 | escrow-mcp | Sovereign data escrow protocol — 7-layer custody, release gates, destruction | Ring 0 |
| 7 | audit-mcp | Immutable audit trail — SIGIL receipts, BFT session transcripts, red-team reports | Ring 0 |
These MCPs ingest sensor and intelligence data from external sources. Data flows inward (from source → DEFONEOS), never outward. AUKUS-compatible but UK-sovereign-controlled.
| # | MCP | Category | Data Direction |
|---|---|---|---|
| 8 | freetak-mcp | C2 / TAK server bridge | Inward |
| 9 | sentinel-hub-mcp | Satellite imagery (Copernicus, Sentinel) | Inward |
| 10 | ais-mcp | Maritime AIS vessel tracking | Inward |
| 11 | gdelt-mcp | OSINT / global news events | Inward |
| 12 | rtsp-mcp | IP camera / RTSP video streams | Inward |
| 13 | yolo-mcp | Computer vision (YOLOv8 object detection) | Inward |
| 14 | athena-mcp | Geospatial query (OpenAthena) | Inward |
| 15 | mava-mcp | Swarm intelligence / multi-agent coordination | Inward |
| 16 | cesium-mcp | 3D globe / digital twin visualization | Inward |
| 17 | mqtt-mcp | IoT bridge / sensor telemetry | Inward |
| 18 | openaq-mcp | Air quality monitoring | Inward |
These MCPs ingest publicly available UK civil data. No classified or sensitive data. Used for situational awareness, planning intelligence, and compliance automation.
| # | MCP | Category |
|---|---|---|
| 19 | os-opendata-mcp | Ordnance Survey open data |
| 20 | data-gov-uk-mcp | data.gov.uk government open data |
| 21 | companies-house-mcp | Companies House registry |
| 22 | ons-mcp | ONS statistics and census |
| 23 | met-office-mcp | Met Office weather data |
| 24 | nhs-mcp | NHS data services |
| 25 | env-agency-mcp | Environment Agency data |
| 26 | transport-mcp | Department for Transport data |
| 27 | planning-mcp | Planning application data |
| 28 | parliament-mcp | UK Parliament data (Hansard, committees) |
| 29 | ofcom-mcp | Ofcom communications data |
| 30 | land-registry-mcp | HM Land Registry data |
Data flows inward only — from external sources through the rings toward the core. Data never flows outward from Ring 0 to Ring 1 or Ring 2 without explicit BFT approval.
At every ring boundary crossing, a SIGIL attestation is generated recording: source MCP, destination MCP, data type, timestamp, Ed25519 signature of approving agent.
Every single tool invocation across all 30 MCPs generates a SIGIL receipt:
| SIGIL Field | Description |
|---|---|
| tick | Global tick counter for ordering |
| mcp_id | Which MCP server was invoked |
| tool_name | Which specific tool was called |
| caller | Ed25519 public key of the calling agent |
| timestamp | RFC3161 trusted timestamp |
| ring | Trust ring of the MCP (0, 1, or 2) |
| data_hash | SHA-256 of input + output data |
| signature | Ed25519 signature of the calling agent |
| ots_proof | Bitcoin OpenTimestamps anchor |
Before any new MCP can join the federation, it must pass all 9 admission control checks, verified by the 33-agent BFT council (23/33 quorum):
| # | Check | Description |
|---|---|---|
| 1 | Source provenance | All code dependencies traced to source, hash-verified |
| 2 | Red-line compliance | MCP contains no kinetic-targeting, no personal-surveillance patterns |
| 3 | Data flow classification | Inward-only data flow confirmed; no outbound data exfiltration |
| 4 | Ring assignment | Correct trust ring assigned based on data sensitivity |
| 5 | SIGIL integration | All tool invocations generate valid SIGIL receipts |
| 6 | UK sovereignty | Ring 0 MCPs: zero external API calls confirmed |
| 7 | Supply chain integrity | No compromised dependencies; SIGIL-anchored on PyPI |
| 8 | Adversarial test pass | Red-team framework: 12 vectors tested, no T1/T2 findings |
| 9 | Escrow compatibility | Any data stored by the MCP is escrow-compatible (7-layer custody) |
New deployments discover the MCP federation via a well-known manifest:
GET /.well-known/defoneos-manifest.json
The manifest contains: list of active MCPs, their trust rings, SIGIL verification endpoints, BFT council status, and federation version. This enables zero-config discovery for new AUKUS partner deployments.
| Ring | Inference Location | External API | Model Access |
|---|---|---|---|
| Ring 0 | UK-sovereign MLX (local) | None | SOV3 sovereign models only |
| Ring 1 | UK-sovereign or AUKUS-partner | AUKUS partners only (BFT-approved) | Sovereign + frontier bridge (BFT-gated) |
| Ring 2 | UK or cloud (unrestricted data) | Any (data is public) | Any model |
| Scenario | Response |
|---|---|
| Single MCP failure | Federation continues. SIGIL records the failure. BFT notified. |
| Ring 0 MCP failure | Governance functions enter safe mode. All data releases frozen. Human-owner notified immediately. |
| Network partition | Each ring operates independently. Ring 0 maintains full governance. Data queued for sync. |
| BFT quorum loss | If <23 agents available, federation enters read-only mode. No new data releases until quorum restored. |
| Escrow breach detected | All Ring 0 MCPs enter emergency freeze. BFT emergency session triggered (17/33). |