AI agents on the substrate.

Five-pattern access architecture

Smart MCP Server is Pattern (e) of the canonical five-pattern access architecture. Each pattern preserves the same Six Non-Modifiable Architectural Commitments (federation by default + per-operation authority + Hub payload-blindness + non-aggregation default + patient-fiduciary doctrine + NO-SHT-BACKDOOR per ADR-032).

• Pattern (a) Cloud Marketplace

  Partners deploy substrate via cloud marketplace listings (AWS Marketplace + Azure Marketplace + GCP Marketplace).

• Pattern (b) TypeScript SDK

  Developers build substrate-using applications programmatically. `@shn/sdk` published via npm; consumes `api.smarthealthhub.net`.

• Pattern (c) Smart Widgets

  Partners embed substrate-rendered UX. `<smart-prior-auth>` + family at `widgets.smarthealthhub.net` CDN.

• Pattern (d) Run-your-own

  Organizations run substrate-coordinator infrastructure (Pattern 2 deployment automation v0.5 IMPL).

• Pattern (e) Smart MCP ServerNEW · this page

  AI agents (Claude Desktop, OpenAI agents, custom enterprise AI) access substrate operations via standard MCP protocol. Sandbox at `sandbox.smarthealthhub.net/mcp`; production at `api.smarthealthhub.net/mcp`.

Endpoints

Documentation lives at developers.smarthealthnetwork.org/mcp (Tier 2 institutional anchor; this page). Operational delivery lives at substrate Hub subdomains per Surface Architecture Brief v1.9:

# Sandbox tier (W6 toolkit synthetic data; Tier 1 self-service onboarding)
https://sandbox.smarthealthhub.net/mcp

# Production tier (HSM-backed substrate operations; Q3 2026 trajectory)
https://api.smarthealthhub.net/mcp

Transport: MCP over JSON-RPC HTTP/HTTPS. Authentication: sandbox API key at sandbox tier; production API key + institutional role-credentialing extension at production tier.

Three deployment topologies

• PBC-operated centralized

  sandbox.smarthealthhub.net/mcp + api.smarthealthhub.net/mcp

  Smart Health Network PBC operates centralized Smart MCP Server endpoints at substrate Hub subdomains. Canonical at substrate-services-v0/services/smart-mcp-server/. Default deployment topology for AI-platform partners and Tier 2 institutional partners adopting Pattern (e) without infrastructure ownership.

• Run-your-own institutional partner

  partner-controlled URL

  Partner deploys Smart MCP Server at partner-controlled URL per partner deployment runbook. Connects to substrate API surface via institutional role-credentialing extension authentication chain. Composes with Pattern (d) Run-your-own / sovereign-equivalence canonical.

• Hybrid

  sandbox.smarthealthhub.net/mcp + partner-controlled production URL

  PBC operates sandbox-tier Smart MCP Server endpoint; partner deploys production-tier Smart MCP Server endpoint at partner-controlled URL. Composes with sovereign-equivalence certification harness composition.

Composition with Smart Widgets (Pattern c)

Pattern (c) Smart Widgets and Pattern (e) Smart MCP Server compose at the same substrate API contract — different consumption-tier surfaces, identical federated query-to-data architectural pattern. AI agent invocations of UC22 Federated Prior Auth via Smart MCP Server route through the same Hub payload-blind transport, same per-operation authority evaluation per ADR-031, same audit chain emission per ADR-022 as Smart Widget invocations. Audit-record canonical distinguishes invocation pattern (Pattern c vs Pattern e vs Pattern a/b/d) cryptographically.

Three-mode multi-audience composition (Mode A provider-embedded · Mode B payer-embedded · Mode C patient-embedded) extends to Pattern (e) invocation context: AI agents invoke federated operations on patient-side credentials (Mode C-equivalent) or provider/payer-side credentials (Mode A/B-equivalent); substrate enforces per-operation authority evaluation IDENTICAL across both patterns.

Status

Smart MCP Server v0.1 DRAFT specification at ADR-XXX Smart MCP Server Architecture (CTO + VP Engineering joint scope; Tier 2 LOCK cycle). MCP Resources / Tools / Prompts canonical specification + AI-agent integration onboarding flow + capability discovery substantive content composes substrate-state-event-paced firing on ADR-XXX v0.2 ratification.

M1 (June 9): sandbox-tier preview surface at sandbox.smarthealthhub.net/mcp. M2 (mid-late June or early-mid July 2026): Anthropic + Smart Health Network substrate-layer joint announcement at Mehmet Oz Delaware CMS event per Q-MCP-C joint disposition.