Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One capture · mcp

One read of Model Context Protocolmcp-20261111T193706Z

3 pages moved out of 360 read.

Pages moved 3 significant first
Pages read 360 in this capture
Captured 19:37 UTC
Corpus hash b01ce77e6cb3 corpus-hash

What this read moved

1-3 of 3

community/working-groups/transports Changed · +5 / -7 lines

from line 12
1212protocol architecture so implementations remain interoperable, scalable, reliable,
1313and easy to operate across local and remote deployments. The WG produces transport
1414proposals, SEPs, implementation evidence, and guidance. The
15[working group repository](https://github.com/modelcontextprotocol/transports-wg) and
16its [upstream charter](https://github.com/modelcontextprotocol/transports-wg/blob/main/CHARTER.md)
17maintain the WG's current technical focus, proposal strategy, and supporting detail
15[working group repository](https://github.com/modelcontextprotocol/transports-wg)
16maintains the WG's current technical focus, proposal strategy, and supporting detail
1817within these boundaries.
1918 
2019## Scope
from line 38
3938* **Validation and Guidance**: Reference implementations, experiments, implementation
4039 evidence, and documentation needed to evaluate proposals and help implementers
4140 adopt agreed transport behavior. Supporting material is maintained in the upstream
42 [documentation](https://github.com/modelcontextprotocol/transports-wg/tree/main/docs).
41 [proposals directory](https://github.com/modelcontextprotocol/transports-wg/tree/main/proposals).
4342 The WG contributes transport scenarios and requirements to the Conformance Testing
4443 project, whose maintainers own the conformance suite.
4544* **Cross-Cutting Coordination**: Transport implications of work owned by other MCP
4645 groups, without taking ownership of their application-layer features.
4746 
48The upstream [scope statement](https://github.com/modelcontextprotocol/transports-wg/blob/main/CHARTER.md#scope)
47The upstream [mission statement](https://github.com/modelcontextprotocol/transports-wg#mission)
4948provides supporting context but cannot expand the boundaries in this charter.
5049 
5150### Out of Scope
from line 121
122121## Resources
123122 
124123* [modelcontextprotocol/transports-wg](https://github.com/modelcontextprotocol/transports-wg)
125 * [Proposals](https://github.com/modelcontextprotocol/transports-wg/tree/main/proposals)
126 * [Supporting documentation and decision records](https://github.com/modelcontextprotocol/transports-wg/tree/main/docs)
124 * [Proposals and decision records](https://github.com/modelcontextprotocol/transports-wg/tree/main/proposals)
127125 * [Meeting notes](https://github.com/modelcontextprotocol/transports-wg/tree/main/meetings)
128126 
129127## Deliverables & Success Metrics

community/interest-groups/security Changed · +0 / -1 lines

from line 119
119119 
120120| Item | Name | Status | Champion |
121121| - | - | - | - |
122| [SEP-2809](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2809) | Attested Tool-Server Admission (ATSA) | Draft | [@metereconsulting](https://github.com/metereconsulting) |
123122| — | SDK vulnerability disclosure | In progress | Facilitators |
124123| — | Runtime drift: `list_changed` semantics after approval | Open | — |
125124| — | Supply-chain integrity: protocol, registry, or companion standard | Open | — |

community/working-groups/governance Changed · +1 / -1 lines

from line 166
166166 
167167This charter is a v0.1 document and is expected to be revised as the group coalesces. Updates
168168follow the
169[Charter Amendments](https://modelcontextprotocol.io/community/working-interest-groups.md#charter-amendments) process defined for
169[charter amendment](https://modelcontextprotocol.io/community/working-interest-groups.md#amending-or-retiring-a-group) process defined for
170170all groups: proposal by a Lead or Core Maintainer, approval by Core Maintainers. Within the WG,
171171amendment proposals are treated like any other substantive governance change — WG consensus
172172first, then Core Maintainer approval. Editorial fixes (typos, broken links, rewordings that do
Feedback