Repository navigation
Proposal: add optional server readiness metadata for enterprise evaluation #4389
Closed as not planned
Description
Summary
modelcontextprotocol/servers is now a critical discovery surface for many teams. For enterprise adoption, maintainers often ask the same trust/readiness questions for each server.
Proposal
Add an optional "Server Readiness Metadata" block (or generated table) per server entry to improve comparability.
Suggested fields:
- Maintainer/org
- Last updated date (or release recency)
- Auth model (none / token / OAuth / delegated)
- Security policy link
- License
- Transport(s) supported (stdio / streamable-http / sse)
- Test status (CI badge or conformance check)
Why this helps
- Faster evaluation for production usage
- Better visibility for well-maintained servers
- Lower repeated due-diligence effort across organizations
I can help propose a markdown schema and a starter PR if maintainers are open to this.
Activity
kmishra1204 commentedon Jun 19, 2026
Opened a docs PR with an optional server readiness metadata template: https://github.com/modelcontextprotocol/servers/pull/4390\n\nIt adds a compact, vendor-neutral metadata block (maintainer, update date, auth model, transports, security link, license).
localden commentedon Jul 29, 2026
Thanks for the interest. We no longer accept server, resource, or tooling submissions to this repository; it is dedicated to the small set of reference servers maintained by the MCP steering group. To make your project discoverable, please publish it to the MCP Registry: https://registry.modelcontextprotocol.io/