Files

T

retoor 251c3dc2ba research: mcp-client-support subject (106 sources, 3 conclusions)

- wire spec: lifecycle, stdio + Streamable HTTP transports, tools,
  utilities, legacy SSE, versioning, changelog (14 Tier 1)
- client ecosystem: Claude Code/VS Code/Cursor/Codex configs,
  mcp-remote, Smithery, registries, Glama (12 Tier 1)
- security/ops: authorization draft, trust model, poisoning,
  rug pulls, production hardening (12 Tier 1) + 68 Tier 2 cards
- conclusions: minimal stdlib client on 2025-11-25, normalizer +
  resolver agent for pasted configs/GitHub URLs, untrusted-until-
  consent trust model; nothing built yet
- audit PASS (14 subjects, 797 sources, 32 conclusions)

2026-10-18 19:23:02 +02:00

3.0 KiB

Raw Blame History

Reference MCP servers repo README (modelcontextprotocol/servers)

Metadata

Field	Value
Institute	Molodetz Institute - Research and Retrieval Division
Subject	mcp-client-support
Document type	Source Dossier
Tier	1
Source title	Reference MCP servers repo README
Source URL	https://github.com/modelcontextprotocol/servers
Source publisher / author	MCP maintainers
Source type	repository
Source date (published)	Unknown, not stated
Date researched	2026-10-18
Researched by	tai (agent), model: Claude Sonnet 5, on behalf of retoor
Research method	gather-subagent direct page fetch, parent synthesis from evidence pack
Confidence	High
Status	Active

Summary

README of the official reference-implementations repo: educational examples, explicitly not production-ready. It fixes the canonical distribution commands (npx -y @modelcontextprotocol/server-memory for TypeScript, uvx mcp-server-git for Python with uvx recommended), the Windows rule (wrap npx with cmd /c, leave uvx unchanged), and warns that many originals are now archived with vendor replacements.

Key findings

"This repository is a collection of reference implementations... intended as... educational examples... not as production-ready solutions."
Canonical TS distribution: "TypeScript-based servers in this repository can be used directly with npx": npx -y @modelcontextprotocol/server-memory.
Canonical Python distribution: "can be used directly with uvx or pip. uvx is recommended": uvx mcp-server-git.
Windows rule: "wrap npx with cmd /c", i.e. "command": "cmd", "args": ["/c", "npx", "-y", ...]; "Leave uvx entries unchanged."
Many originals (GitHub, GitLab, Postgres, SQLite, Slack, Brave Search, Puppeteer...) are now Archived at servers-archived, several replaced by official vendor servers (e.g. Brave, Zencoder's Slack): repo READMEs go stale; prefer vendor repos.

Pros / strengths

Gives the exact canonical commands for both language tracks plus the Windows cmd /c rule, which is directly codeable as generation logic.
The archived-vs-vendor warning is a real data-quality rule: prefer vendor repos over this repo's READMEs.
Maintainer-authored, so the "reference, not production" framing is honest scope-setting rather than a gap.

Cons / limitations / caveats

No publish date; archival migrations continue, so any server list derived from this repo rots fast.
Reference-only framing means production run details (auth, secrets, hosting) are out of scope here by design.
Covers the happy path for TS/Python only; other runtimes get no canonical command.

Relevance to tai

Grounds the npx/uvx/cmd /c command-generation rules and warns that GitHub READMEs may point at archived predecessors. The prefer-vendor-repos rule is a direct input to tai's source-priority ordering.

Changelog

Date	Change
2026-10-18	Initial dossier created.

3.0 KiB Raw Blame History