Technology · Agentic → Agentic Gateways · Open Source · wiki:deep
The modelcontextprotocol/servers repository is the official/reference collection of MCP servers (filesystem, git, memory, and more). It is the baseline capability pack for bootstrapping an MCP tool bus. Use as examples and starting points; production OS installs should fork/pin approved servers and put them behind gateway policy rather than running the whole public set unchecked. Model Context Protocol Servers This repository is a collection of reference implementations for the Model Context Protocol (MCP), as well as references to community-built servers and additional resources. [!IMPORTANT] If you are looking for a list of MCP servers, you can browse published servers on the MCP Registry. The repository served by this README is dedicated to housing just the small number of reference servers maintained by the MCP steering group. [!WARNING] The servers in this.
In this catalog it is the Agentic Gateways option when you need to front agents and MCP/tool surfaces safely. Keep MCP Servers (reference) on the observe/propose side of the loop: useful signals and drafts, with human or policy authority still required before anything irreversible runs.
Clients connect to the gateway/registry; it authenticates, discovers MCP/agent servers, and proxies tool or agent traffic under configured policy.
Related: model-context-protocol · fastmcp · mcp-registry · topics/33-skill-registry · topics/12-central-nervous-system
Claims below are backed by science sources on disk.
Primary / product role
Host/client/server security boundaries · MODERATE
“This repository is a collection of reference implementations for the Model Context Protocol (MCP), as well as references to community-built servers and additional resources.”
Docs or contrast
modelcontextprotocol/servers · MODERATE
“The servers in this repository showcase the versatility and extensibility of MCP”
Additional source
MCP specification (tools/resources/prompts) · MODERATE
“Developers should evaluate their own security requirements and implement appropriate safeguards based on their specific threat model and use case.”
9 tags · 20 out · 21 in · 3 artifacts · 0 gaps · 15 corpus docs
map_edge · 6
tech_features · 1
tech_quote · 7
tech_readme · 1