Skip to content
AdminKit

JSON-RPC

What is JSON-RPC?

JSON-RPC is a lightweight remote-procedure-call format, specified at jsonrpc.org, that encodes a method, parameters and an ID as JSON. Version 2.0 is the wire format the Model Context Protocol requires for every client-server message. AdminKit's MCP endpoint check probes a server's initialize and tools/list JSON-RPC calls directly.

By AdminKit team, Netbase JSC · Updated

JSON-RPC is a lightweight remote procedure call protocol, specified at jsonrpc.org, that encodes a method name, parameters, and an identifier as a JSON object, letting one system ask another to run a named operation and return a result or error in a matching JSON reply. The JSON-RPC specification names JSON, citing RFC 4627, as its data format and shares JSON’s type system of four primitive and two structured types; JSON’s current IETF standard is RFC 8259, which superseded that earlier RFC. Version 2.0, the version in current use, is the wire format the Model Context Protocol (MCP) builds on: an MCP client sends JSON-RPC requests like initialize, tools/list or completion/complete to a server, which responds with a JSON-RPC result carrying its capabilities or exposed tools. Because JSON-RPC itself defines only the message shape, not authentication or transport security, an MCP server’s actual protection against unauthorized calls depends entirely on what the server (or a gateway in front of it) adds on top. JSON-RPC 2.0 is also one of the interchangeable bindings the A2A (Agent2Agent Protocol) specification defines for agent-to-agent communication.

AdminKit groups jSON-RPC under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What version of JSON-RPC does MCP require?

Version 2.0 -- it's the wire format every MCP client-server message builds on, carrying a method, parameters and an ID (or no ID for a notification).

Does JSON-RPC itself handle authentication or transport security?

No -- JSON-RPC defines only the message shape, so an MCP server's actual protection against unauthorized calls depends entirely on what the server or a gateway in front of it adds.

What's an example of a JSON-RPC request an MCP client sends?

initialize and tools/list are two common ones, each a JSON-RPC request the server answers with a matching JSON-RPC result.