Skip to content
PointSav Digital Systems

MCP as substrate protocol

← All revisions

2e2eaba7 · PointSav Digital Systems ·

docs(substrate): add external references to llm-substrate-decision and mcp-substrate-protocol (4 files, 2 bilingual pairs)

View the full record as of this revision →

@@ -8,9 +8,13 @@ quality: published
short_description: "Every Foundry Ring 1 and Ring 2 service exposes a Model Context Protocol server interface as its primary external contract, with the Doorman as the MCP gateway."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-05-01
last_edited: 2026-05-15
editor: pointsav-engineering
cites: []
references:
  - id: 1
    text: "Anthropic. 'Model Context Protocol Specification.' modelcontextprotocol.io, 2025."
    url: "https://modelcontextprotocol.io/specification/2025-11-25"
paired_with: mcp-substrate-protocol.es.md
---

@@ -18,7 +22,7 @@ paired_with: mcp-substrate-protocol.es.md

## Why MCP is substrate-level

The Model Context Protocol has become the industry standard for AI-native application composition. It defines a stable, machine-readable interface between clients, servers, and host processes. Foundry adopts it at the substrate level because the alternative — bespoke per-service wire formats — accumulates versioning debt, per-pair contract testing costs, and custom client implementations in every consumer. MCP is the coordination point that prevents that drift.
The Model Context Protocol has become the industry standard for AI-native application composition. It defines a stable, machine-readable interface between clients, servers, and host processes. [^1] Foundry adopts it at the substrate level because the alternative — bespoke per-service wire formats — accumulates versioning debt, per-pair contract testing costs, and custom client implementations in every consumer. MCP is the coordination point that prevents that drift.

The practical result: a customer-built agent, an IDE extension, and the Foundry operator TUI all interact with the same service interfaces using the same protocol. There is no "developer API" distinct from the "user API." The wire contract is unified.

@@ -63,8 +67,3 @@ The Doorman's existing OpenAI-compatible HTTP interface is preserved alongside M
- [[code-for-machines-first]] — MCP as the structural realization of machine-first service contracts
- [[vertical-seed-packs-marketplace]] — planned packs ship with vertical-specific MCP server extensions

## References

1. Doctrine claim #46 — MCP-as-Substrate-Protocol (ratified v0.1.0).
2. MCP specification — https://modelcontextprotocol.io/specification/2025-11-25
3. `conventions/single-boundary-compute-discipline.md` — claim #43 composition.
Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →