Reference Server Inventory Verification

[fjcobu14]

This issue tracks the verification of the inventory of currently maintained (non-archived) reference MCP servers in this repository.

Verification scope:

• Count of active reference servers listed in the README
• Names of each active reference server
• Confirmation that each listed server's package manifest (package.json for TypeScript servers, pyproject.toml for Python servers) exists in its source directory
• Review of any related open issues that could affect the count or status

Findings to be documented in comments.

[fjcobu14]

Verified Reference Server Inventory

Verified Count: 7 non-archived reference MCP servers

The README "Reference Servers" section lists exactly 7 active (non-archived) servers. Each was verified by confirming that its package manifest exists in the corresponding source directory within this repository.

Complete List of Server Names:

#	Server Name	Source Directory	Package Manifest	Language	Verified
1	Everything	src/everything	package.json (@modelcontextprotocol/server-everything v2.0.0)	TypeScript	✅
2	Fetch	src/fetch	pyproject.toml (mcp-server-fetch v0.6.3)	Python	✅
3	Filesystem	src/filesystem	package.json (@modelcontextprotocol/server-filesystem v0.6.3)	TypeScript	✅
4	Git	src/git	pyproject.toml (mcp-server-git v0.6.2)	Python	✅
5	Memory	src/memory	package.json (@modelcontextprotocol/server-memory v0.6.3)	TypeScript	✅
6	Sequential Thinking	src/sequentialthinking	package.json (@modelcontextprotocol/server-sequential-thinking v0.6.2)	TypeScript	✅
7	Time	src/time	pyproject.toml (mcp-server-time v0.6.2)	Python	✅

Verification Method:

• Cross-referenced the README "🌟 Reference Servers" section against the source tree
• For each listed server, confirmed the package manifest (package.json for TypeScript servers, pyproject.toml for Python servers) exists at the path indicated in the README
• All 7 README entries map to real, existing source directories with valid package manifests

Related Open Issues Reviewed:

• server-memory and server-sequential-thinking fail at startup due to missing zod dependency #4330 — server-memory and server-sequential-thinking fail at startup due to missing zod dependency in published npm packages. This is a runtime dependency bug that does not affect the server count or the existence of source code; the package.json files in the repo correctly list zod as a dependency.
• Several @modelcontextprotocol/server-* packages on npm appear stale (no recent releases, no repo URL in package.json) #4266 — Several archived @modelcontextprotocol/server-* npm packages appear stale. All servers mentioned (postgres, gdrive, github, slack, puppeteer) are already listed under the "Archived" section in the README and are excluded from the active reference server count.
• zod declared in both dependencies and peerDependencies causes ERR_MODULE_NOT_FOUND with pnpm strict isolation #4288 — zod declared in both dependencies and peerDependencies causes module resolution issues with pnpm strict isolation. A dependency packaging concern, not an inventory issue.

Archived Servers (excluded from count):

The README lists 13 archived servers (AWS KB Retrieval, Brave Search, EverArt, GitHub, GitLab, Google Drive, Google Maps, PostgreSQL, Puppeteer, Redis, Sentry, Slack, SQLite) that have been moved to the servers-archived repository. These are not counted as active reference servers.

Verified count: 7 active (non-archived) reference MCP servers.