Authority profile · compiled by Lazyweb
David Soria Parra
MCP co-inventor and lead maintainer.
David Soria Parra co-invented the Model Context Protocol and serves in its governance. His writing is the shortest route to the protocol's design intent, evolution and operating model.
Original profile or publication
MCP governance identifies David as a co-inventor and lead maintainer; portrait comes from the linked public GitHub profile. Checked September 19, 2026.
- Updated
Referenced in 101
- MCP 101
MCP architecture
A host owns user experience and security boundaries, clients maintain one server connection each, and servers expose focused context and capabilities. - MCP 101
MCP transports
Local stdio and remote Streamable HTTP solve different connection problems while carrying the same protocol messages. - MCP 101
Build an MCP server
Start with one useful capability and a supported SDK, then prove the server through an inspector or real host before adding breadth. - MCP 101
MCP authorization
Remote MCP authorization builds on OAuth while keeping resource servers, authorization servers, clients and protected resources explicit. - MCP 101
MCP authorization security considerations
Token passthrough, confused deputies, open redirects and excessive scopes turn a convenient connector into an account-compromise path. - MCP 101
MCP's first anniversary
MCP's first year moved the protocol from an Anthropic launch to broad infrastructure with a community process and a much larger compatibility burden. - MCP 101
Introducing the MCP Registry
A shared registry standardizes discovery metadata; it does not certify server quality, safety, uptime or real tool execution. - MCP 101
The MCP roadmap
The roadmap identifies the protocol's active pressure points so builders can avoid treating current gaps as permanent architecture.
About this page
This is a Lazyweb reference profile, not an account, endorsement or claim that David Soria Parra contributed to Lazyweb. The profile identifies an author, editor, maintainer, speaker or source publication connected to the linked work; it is not necessarily the article byline. Summaries are Lazyweb's; the linked work remains the source of truth.