MCP Reference Servers
Anthropic's official collection of reference Model Context Protocol server implementations across languages.
- Sato Score72
MCP Reference Servers is an open-source developer tool by Anthropic, with last code activity on 2026-10-11 (Active). Latest release on 2026-10-11. Sato Score 72/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install MCP Reference Servers →Last commit Oct 7, 2026 · Last release Oct 11, 2026 (v1.0.0) · ★ 91,080
Listed from github.com/modelcontextprotocol/servers on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch MCP Reference Servers
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on modelcontextprotocol/servers before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
MCP Reference Servers is Anthropic's official repository of educational, reference-grade Model Context Protocol server implementations (Git, Filesystem, Memory, Fetch, and more) spanning Python, TypeScript, Go, and Rust. It exists to demonstrate MCP SDK usage and protocol features for developers building their own servers, not as production-hardened infrastructure. A builder uses it as the canonical starting point and pattern library when implementing a new MCP server for an agent.
Sato Score
72/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 20/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 2/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.0.0 · as of 2026-10-11- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run · earlier run 2026-09-25: not observed
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from github.com/modelcontextprotocol/servers on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | not stated | self-reported | github.com/modelcontextprotocol/servers | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | github.com/modelcontextprotocol/servers | as of 2026-10-15 |
| Recent activity | last release 2026-10-11 · last commit 2026-10-07 | observed | github.com/modelcontextprotocol/servers | 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/modelcontextprotocol/servers | 2026-07-21 |
| Website answers | answered (HTTP 200) | observed | github.com/modelcontextprotocol/servers | 2026-10-15 |
| Daily check record | 89 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-10-11 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-10-11 |
| Sato Score | 72/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Jul 21, 2026
Runtime: node
npx -y @modelcontextprotocol/server-everything
{"mcpServers": {"everything": {"command": "npx", "args": ["-y", "@modelcontextprotocol/server-everything"]}}}claude mcp add satohub-mcp-reference-servers -- npx -y @modelcontextprotocol/server-everything
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 90
- Failed
- 1
- Their error
- 0
- Unattributed
- 1
State changed on 2026-09-21 (responding → unreachable from our probe), 2026-09-22 (unreachable from our probe → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Unknown
- Agent types
- MCP Server, Developer Agent
- Open source
- Yes
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Recent Activity
All news →Releases and posts from MCP Reference Servers, pulled from its GitHub and X.
servers v1.0.0
Packages Package Version Registry In this release @modelcontextprotocol/server-everything 1.0.0 npm published @modelcontextprotocol/server-filesystem 1.0.0 npm published @modelcontextprotocol/server-memory 1.0.0 npm published @modelcontextprotocol/server-sequential-thinking 1.0.0 npm published mcp-server-fetch 2026.10.10 PyPI published mcp-server-git 2026.10.10 PyPI published mcp-server-time 2026.
servers Release 2026.8.31
Release : v2026.8.31 Updated packages @modelcontextprotocol/server-filesystem@2026.8.31 @modelcontextprotocol/server-memory@2026.8.31 @modelcontextprotocol/server-sequential-thinking@2026.8.31 @modelcontextprotocol/server-everything@2026.8.31
servers Release 2026.8.18
Release : v2026.8.18 Updated packages @modelcontextprotocol/server-everything@2026.8.18 mcp-server-time@2026.8.18 mcp-server-fetch@2026.8.18 mcp-server-git@2026.8.18
servers Release 2026.7.10
Release : v2026.7.10 Updated packages @modelcontextprotocol/server-filesystem@2026.7.10 mcp-server-time@2026.7.10 mcp-server-fetch@2026.7.10 mcp-server-git@2026.7.10
Listing History
Recorded changes to MCP Reference Servers's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 11, 2026New release published
- Aug 31, 2026New release published
- Aug 18, 20263 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Jul 21, 2026Verified: deploy spec
- Jul 20, 2026Sato Score tier: Medium → HighScore 62 → 70.
- Jul 19, 2026Sato Score tier: High → MediumScore 72 → 62.
- Jul 18, 2026Auto-enriched: docs url, deployment options
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Jupiter
ActiveSolana swap aggregator that routes trades across DEXs via a widely used API and SDKs.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about MCP Reference Servers
- Is MCP Reference Servers open source?
- Yes. MCP Reference Servers is open source under the MIT/Apache-2.0 (transitioning; new contributions Apache-2.0, some existing MIT) license; the repository is https://github.com/modelcontextprotocol/servers. Checked as of 2026-10-15.
- Which chains does MCP Reference Servers support?
- Sato Hub has no confirmed chain list for MCP Reference Servers as of 2026-10-15; treat chain support as unknown.
- Is MCP Reference Servers still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-11 (last commit 2026-10-07, last release 2026-10-11), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run MCP Reference Servers?
- node. Install: npx -y @modelcontextprotocol/server-everything. Entry: {"mcpServers": {"everything": {"command": "npx", "args": ["-y", "@modelcontextprotocol/server-everything"]}}}. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y @modelcontextprotocol/server-everything).
- Is MCP Reference Servers verified on Sato Hub?
- Sato Hub holds one earned check for MCP Reference Servers: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 72 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "MCP Reference Servers — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/mcp-reference-serversData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.