docs: stop claiming the host sees only ciphertext (#635)

The README said the connectivity provider sees ciphertext and nothing but the
signed claim leaves the enclave. The docs landing says host confidentiality
depends on the egress policy and the upstream tool server sits outside the
TEE, and LIMITATIONS.md lists what cMCP does not prevent. The README now says
the same, and that software mode has no hardware isolation.

Also: the charter named MCP as Anthropic's, but MCP moved to the Agentic AI
Foundation on 2025-12-09. The sponsor pages and ADOPTERS.md name OPAQUE as
sponsor without the ownership disclaimer, and the social card alt text no
longer calls cMCP a standard.


Claude-Session: https://claude.ai/code/session_013aK3gVWzNdcM3hZ2o2awK2

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: imran-siddique

ADOPTERS.md

@@ -3,8 +3,7 @@
 Organizations using cMCP in production or evaluation are listed here.
 
 Project funding and in-kind support are recognized separately in
-[SPONSORS.md](SPONSORS.md). Sponsorship does not imply adoption, governance
-authority, or ownership of the project.
+[SPONSORS.md](SPONSORS.md).
 
 To add yours, open a PR adding a line with your organization, the use case, and the month you started. Anything you are not able to say publicly, leave out; a one-line entry is worth more than a case study you have to get approved.
 

CHARTER.md

@@ -59,7 +59,7 @@ Use of "cMCP-compatible" to describe a gateway deployment requires that the impl
 
 cMCP builds on and does not replace:
 
-- **MCP (Model Context Protocol, Anthropic)**: the underlying tool-call protocol that cMCP extends with attestation
+- **MCP (Model Context Protocol, Agentic AI Foundation)**: the underlying tool-call protocol that cMCP extends with attestation
 - **TRACE** ([agentrust-io/trace-spec](https://github.com/agentrust-io/trace-spec)): governance record emitted per attested tool call
 - **Agent Manifest** ([agentrust-io/agent-manifest](https://github.com/agentrust-io/agent-manifest)): agent identity bound at tool-call time
 - **SPIFFE / SPIRE**: workload identity for gateway and agent services

README.md

@@ -48,7 +48,7 @@ The control plane that governs tool calls must run where it cannot be reached by
 
 Hardware-attested policy enforcement for MCP tool calls. Every tool call is intercepted, evaluated against a Cedar policy bundle, and enforced by a policy engine running inside a Trusted Execution Environment (TEE). The policy bundle hash is measured into the hardware attestation report before any code runs.
 
-Unlike tunnel-based connectivity solutions, the cMCP Runtime processes tool-call payloads inside the TEE. The connectivity provider sees ciphertext, not plaintext. The only thing that leaves the enclave is the signed TRACE claim.
+In a hardware deployment, the cMCP Runtime processes tool-call payloads inside the TEE. What the host and connectivity provider can read also depends on the egress policy, and the upstream tool server is a separate component outside the TEE. Software mode (`CMCP_DEV_MODE`) provides no hardware isolation. [LIMITATIONS.md](LIMITATIONS.md) lists what cMCP does not prevent.
 
 ---
 

SPONSORS.md

@@ -1,9 +1,9 @@
 # Sponsors
 
-cMCP is an open-source AgenTrust project governed through its published
-project processes. Sponsors provide funding, engineering time, infrastructure,
-or other in-kind support. Sponsorship does not confer project ownership,
-governance authority, or control over technical decisions.
+cMCP is an open-source AgenTrust project. It is sponsored by OPAQUE Systems,
+which funds the engineering, infrastructure and confidential-computing work
+behind it. Organisations that want to support the project are welcome to join
+as sponsors.
 
 ## Current sponsors
 

docs/sponsors.md

@@ -1,10 +1,9 @@
 # Sponsors
 
-cMCP is an open-source AgenTrust project. Sponsors support the project without
-receiving project ownership or governance authority.
-
-OPAQUE Systems is recognized as a founding engineering and infrastructure
-sponsor and as a contributor to the project's confidential-computing
-integrations.
+cMCP is an open-source AgenTrust project. It is sponsored by OPAQUE Systems,
+which funds the engineering, infrastructure and confidential-computing work
+behind it and contributes to the project's confidential-computing
+integrations. Organisations that want to support the project are welcome to
+join as sponsors.
 
 See the repository's [sponsor policy and recognition page](https://github.com/agentrust-io/cmcp/blob/main/SPONSORS.md) for details.

overrides/main.html

@@ -23,7 +23,7 @@
   <meta property="og:image" content="{{ config.site_url }}assets/og.png">
   <meta property="og:image:width" content="1200">
   <meta property="og:image:height" content="630">
-  <meta property="og:image:alt" content="cMCP: an AgenTrust open standard">
+  <meta property="og:image:alt" content="cMCP: part of the AgenTrust verifiable AI supply chain">
 
   <meta name="twitter:card" content="summary_large_image">
   <meta name="twitter:title" content="{% if page_name %}{{ page_name }} - {{ config.site_name }}{% else %}{{ config.site_name }}: Confidential MCP Runtime{% endif %}">