Glossary
MCP server
A process that exposes tools, resources and prompts to an AI agent over the Model Context Protocol, so the agent discovers what it can call at connect time.
The Model Context Protocol is a JSON-RPC protocol between an agent host (a client) and a server. On connect the two exchange an initialize handshake; the client then calls tools/list to learn what the server offers and tools/call to use one. Transports are stdio for a local process or Streamable HTTP for a hosted endpoint. A crypto MCP server typically wraps chain reads, a wallet, a DEX or a data API behind that interface.
Sato Hub distinguishes a listing that implements MCP (the interface is in its record) from one with a hosted endpoint (a URL Sato Hub can call). The hosted ones are probed daily: Sato Hub performs the handshake and asks for the tool list, and records whether that succeeded. Sato Hub's own directory is itself an MCP server.
An MCP server that answers is live; it is not thereby correct, safe to give a key to, or maintained. A tool named swap does whatever its code does. The daily check measures the interface, nothing behind it.
Where Sato Hub measures it
- MCP server status — today's check per hosted endpoint →
- Reliability index →
- Hosted MCP endpoints answering today, scored →
- MCP implementations in the directory →
- Sato Hub's own MCP server →
Numbers live on those pages and refresh on their own schedule; this definition does not restate them.
Related terms
Sources
Cite this page
Sato Hub. "MCP server (glossary)." Sato Hub, accessed 2026-09-09. https://satohub.ai/glossary/mcp-serverThis page is refreshed daily. Citations include the date so a reader can tell which snapshot a claim came from.