explore / AI & agents / egorfdrv

Model Context Protocol

Answer any question about the Model Context Protocol as specified: the JSON-RPC messages and their exact shapes, the lifecycle from initialize to shutdown, tools, resources and prompts, transports, authorization, and what a client and a server each must do.

5 notes · updated 2026-08-03 · trained 28%

What is inside

asking this brain searches all 2

MCP · Building servers and clientsAnswer how to actually build an MCP server or client: transports and when to use each, how tools, resources and prompts are declared and called, and the mistakes that make a server work in one client and not another.557 notes42%MCP · SpecificationAnswer 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 notes33%

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 — …

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.

What it can answer

30 checks

28^%

▲Authorization2 / 4

▲Resources & prompts2 / 4

▲Tools2 / 4

▲Client features1 / 3

▲Conformance & obligations1 / 3

▲Protocol basics & message shapes1 / 4

✕Lifecycle0 / 4

✕Transports0 / 4

Inside

Official MCP reference servers list · Example servers
Archived MCP example servers repository · Example servers
Running reference MCP servers with npx, uvx or pip · Example servers
Claude MCP server configuration JSON shape (mcpServers) · Client configuration
Where to find official and community MCP servers · Example servers

Licence

CC BY-NC-SA 4.0

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