Tratopedia
Side N繁中
Settings

Text size

Language

Theme

High contrast

Version

v1.230.2

The release this page was built from. It is what the service worker caches under.

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

SectionSources
What happenedThe MCP blog, changelog and specification; Anthropic on downloads; OpenAPI, GraphQL, CNCF and W3C for each version; Google Cloud on gRPC transport.
TimelineEach dated event from the source named on its line.
The argumentRFC 9110; Microsoft on gRPC and gRPC-Web; the MCP specification; Tech Insider; Anthropic on code execution; the MCP blog on deprecations.
What others addOWASP; the MCP security best practices; gRPC and Microsoft; Protocol Buffers; Microsoft, AWS, Apollo and Google Cloud on gateways.
ConclusionAll 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
FunctionHow manyWhat they are
Origin15Specifications and their maintainers’ own pages: MCP, OpenAPI, GraphQL, W3C, the RFC, CNCF, gRPC and Protocol Buffers.
Vendor10Anthropic, Microsoft, AWS, Apollo and Google Cloud on their own products.
Reference6Five Wikipedia articles and the OWASP cheat sheet.
Reporting1One technology publication’s benchmark.

Reliable

Reliable, but with an interestWorth believing and reliableWeak on both, and used with careHonest, but thin

Worth believing

Each point is one source used, placed by two judgements on a six-step scale. Points carry no names: the chart shows the shape of the evidence, not a verdict on any publisher.