-
Notifications
You must be signed in to change notification settings - Fork 7
Meeting on November 6th, 2025
Atul Tulshibagwale edited this page Nov 6, 2025
·
1 revision
| Name | Affiliation | Participation Agreement signed? |
|---|---|---|
| Atul Tulshibagwale | SGNL | Yes |
| Tobin South | Stanford / WorkOS | Yes |
| Jeff Lombardo | AWS | Yes |
| Flemming Andreasen | Cisco | Yes |
| Hob Spillane | Workday | Yes |
| Stan Bounev | Blue Label Labs | Yes |
| Andy Lim | Cisco | Yes |
| Nick Dawson | Self | Yes |
| Eleanor Meritt | Self | Yes |
| Adwait Shinganwade | Independent | Yes |
| Naveen CM | Yahoo | Yes |
| Sarah Cecchetti | Beyond Identity | Yes |
| Tal Skverer | Astrix Security | Yes |
| Uday Hari | Self | Yes |
| Julie Maas | EMR Direct and UDAP.org | Yes |
| Tom jones | ind | y |
| Bertrand CARLIER | Wavestone | yes |
| Paul Lanzi | IDenovate | yes |
| Alex Babeanu | Indykite | yes |
- Tobin’s weekly updates (5 minutes)
- MCP Server security analysis survey results - Tal Skverer (15 minutes)
- AI identity use cases discussion led by Tobin (10 minutes)
- AIIM meeting schedule starting 11/13
- AOB
- OOB elicitation
- Specs to implement for MCP authorization: [external] SEPs to implement for 25-11-2025
- (Jeff) AI discussions in IETF
- (Atul) ext-auth extensions to MCP
- Enterprise Managed Auth based on Aaron P’s Cross App Access
- IETF wg progress on this?
- (Sarah) CIMD is accepted in the spec but uses URLs for client IDs, this requires extra handling of url edge cases and makes it incompatible with SPIFFE
- (Jeff) SPIFFE identified are not routable
- Tal Skverer is the presenter
- Slide deck: State of MCP Server Identity Security
- Secret Wrapper Tool: https://github.com/astrix-security/mcp-secret-wrapper
- (Tobin) It’s interesting to see so many servers not support any authorization, when many registries don’t even allow such servers to be listed. Are these nonsense servers?
- (Sarah) Customers are demanding it, so they’re just wrapping their APIs, using existing authorization model (API keys)
- (Tobin) Since its been so slow for MCP clients to adopt OAuth, how many servers will actually implement all the new specs we are defining. Here’s the list of clients: https://modelcontextprotocol.io/clients
- (Alex) asks how MCP clients should tackle the cases where the MCP serves multiple tenants and exposes a list of AS’s in its metadata? There’s no easy way currently for a client to determine which to use if the answer is not obvious.
- (Bhavna) How do we ensure Safe MCP compliance
- (Sarah) Profiles could be a way to do it. We could define a Healthcare profile or a Financial Services profile, etc.
- (Jeff) Just like OIDC for Financial services is FAPI, we could have some profile like that of MCP
- (Elenor) What happened to profiles
- (Atul) They are now extensions: https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1724