One read of Model Context Protocolmcp-20261031T160706Z
2 pages moved out of 359 read.
Pages moved
2
significant first
Pages read
359
in this capture
Captured
16:07 UTC
Corpus hash
194f0df56f24
corpus-hash
What this read moved
1-2 of 2community/interest-groups/security Changed · +14 / -7 lines
from line 8
88
99## Mission Statement
1010
11The Security Interest Group catalogs MCP-specific threats, reviews security-relevant proposals, and
12scopes validated problems into focused Working Groups or [SEPs](https://modelcontextprotocol.io/community/sep-guidelines.md).
11The Security Interest Group is the first stop for MCP-specific security topics. It vets incoming
12threats, security-relevant proposals, and disclosure questions, then routes validated work to the
13Working Group or [SEP](https://modelcontextprotocol.io/community/sep-guidelines.md) that owns it.
1314
1415## Scope
1516
1617### In Scope
1718
19* **Triage and routing**: receiving security topics raised on Discord or GitHub and handing them
20 to the owning group (Auth IG, Transports WG, Registry WG, Tool Annotations IG, SDK maintainers)
1821* **Threat modeling**: developing and maintaining a shared, layered view of MCP attack surfaces
1922 spanning admission and identity, caller governance, runtime behavior, interception and enforcement,
2023 and auditability, to give individual proposals a common frame of reference
from line 91
8891| Stefano Ortolani | Broadcom | [@ostefano](https://github.com/ostefano) | `ostefano.` | Participant |
8992
9093Open to anyone. Join the `#security-ig` channel on the
91[MCP Contributors Discord](https://modelcontextprotocol.io/community/communication.md#discord). Calls are open and active
92participation is highly encouraged. The group is looking for contributors who will engage with
93proposals and help drive work forward rather than observe.
94[MCP Contributors Discord](https://modelcontextprotocol.io/community/communication.md#discord). Discussion runs asynchronously in
95the channel between calls, and the agenda for each monthly call is assembled there. The group is
96looking for contributors who will engage with proposals and help drive work forward rather than
97observe.
9498
9599## Operations
96100
97101| Meeting | Frequency | Duration | Purpose |
98102| - | - | - | - |
99| Office Hours | Every 2 weeks | 45 min | Threat review, proposal triage, deployment reports, WG-proposal scoping |
103| Forum call | Monthly | 45 min | Triage and routing of topics on the published agenda, WG proposal scoping |
104| Digest | Monthly | n/a | Summary of routed items, open topics, and advisories |
100105
101An agenda is shared in `#security-ig` ahead of each call.
106The facilitators post a call for agenda in `#security-ig` ahead of each monthly call, and anyone
107can add topics to it.
102108
103109Discord: [#security-ig](https://discord.com/channels/1358869848138059966/1379811011669921883)
104110
from line 130
124130
125131| Date | Change |
126132| - | - |
133| 2026-08-26 | Restructured as a routing group, replaced biweekly office hours with a monthly agenda-driven call and digest (core maintainer meeting, [discussion #3316](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/3316)) |
127134| 2026-06-13 | Initial charter |
128135
community/security Changed · +3 / -3 lines
from line 61
6161
6262## Security Interest Group
6363
64The [Security Interest Group](https://modelcontextprotocol.io/community/interest-groups/security.md) is the venue for
65discussing MCP-specific threats, reviewing security-relevant proposals, and routing
66disclosure questions that don't fit a single repository.
64The [Security Interest Group](https://modelcontextprotocol.io/community/interest-groups/security.md) is where you raise MCP-specific
65security topics, including disclosure questions that don't fit a single repository, and where
66facilitators route them to the group that owns the work.
6767