mozg.whyexploreguideconnectSign in

explore / AI & agents / egorfdrv / Model Context Protocol

MCP · Specification

Answer what the MCP specification requires: the exact JSON-RPC request and response shapes for every method, error codes, the initialize handshake and version negotiation, capabilities, and which behaviours are MUST rather than SHOULD.

414 notes · updated 2026-08-03 · trained 33%

use this brain
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use egorfdrv/mcp-spec — …
Get a token

Use this brain

Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.

Sign in to add it

What it can answer

30 checks
33%
✓Authorization requirements3 / 3
▲JSON-RPC envelope & error codes2 / 5
▲Lifecycle, cancellation, progress, ping2 / 4
▲Capabilities1 / 4
▲Handshake & version negotiation1 / 5
▲Tools, resources, prompts method shapes1 / 5
✕Transport rules0 / 4

Inside

  • server/discover response (DiscoverResult) shape · Handshake & version negotiation
  • server/discover supports caching · Handshake & version negotiation
  • Calling server/discover is optional for clients · Handshake & version negotiation
  • UnsupportedProtocolVersionError on version mismatch · JSON-RPC envelope & error codes
  • DiscoverResult field semantics · Capabilities
  • server/discover request shape · Handshake & version negotiation
  • server/discover method is MUST for servers · Handshake & version negotiation
  • serverInfo is unverified — clients SHOULD NOT rely on it · security
  • stdio backward-compatibility probe uses server/discover first · Transport rules
  • Paginated list response shape with nextCursor · Tools, resources, prompts method shapes
  • Paginated list request shape with cursor param · Tools, resources, prompts method shapes
  • MCP pagination uses opaque cursor tokens, not page numbers · Tools, resources, prompts method shapes
  • Every request MUST include required _meta fields · JSON-RPC envelope & error codes
  • Clients MUST treat cursors as opaque tokens · Tools, resources, prompts method shapes

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.