Side N
REST, SOAP, gRPC, GraphQL and MCP: pick by who calls
Which sources back which section of this article, and what its evidence base looks like.
Which sources back which section
| Section | Sources |
|---|---|
| What happened | The MCP blog, changelog and specification; Anthropic on downloads; OpenAPI, GraphQL, CNCF and W3C for each version; Google Cloud on gRPC transport. |
| Timeline | Each dated event from the source named on its line. |
| The argument | RFC 9110; Microsoft on gRPC and gRPC-Web; the MCP specification; Tech Insider; Anthropic on code execution; the MCP blog on deprecations. |
| What others add | OWASP; the MCP security best practices; gRPC and Microsoft; Protocol Buffers; Microsoft, AWS, Apollo and Google Cloud on gateways. |
| Conclusion | All of the above, as in the sections. |
What the evidence base looks like
- 32Sources used on the page
- 32Read in full at their own pages
- 1Independent performance benchmarks
| Function | How many | What they are |
|---|---|---|
| Origin | 15 | Specifications and their maintainers’ own pages: MCP, OpenAPI, GraphQL, W3C, the RFC, CNCF, gRPC and Protocol Buffers. |
| Vendor | 10 | Anthropic, Microsoft, AWS, Apollo and Google Cloud on their own products. |
| Reference | 6 | Five Wikipedia articles and the OWASP cheat sheet. |
| Reporting | 1 | One technology publication’s benchmark. |
Reliable
Reliable, but with an interestWorth believing and reliableWeak on both, and used with careHonest, but thin
Worth believing