modelcontextprotocol/registry

View on GitHub

A community driven registry service for Model Context Protocol (MCP) servers.

Stars: 7.3k
Forks: 994
Open beginner issues: 0
Indexed issues: 113
Avg merge: 4d 12h
Merged PRs (30d): 19

Dominant language: Go
License: No license data
Last GitHub push: Sep 16, 2026
Latest indexed: Sep 20, 2026
Contributing guide: Contributing guide
Code of conduct: Code of conduct
Beginner labels: help wanted

Beginner friendly Everything

Open All

113 open issues indexed

Trust at first contact for MCP: adopt AID DNS record + key handshake (portable, decentralized, ongoing) Open

enhancement v1

Difficulty 5/5 Over a week Newbie friendliness 25/100

modelcontextprotocol/registry#406 · 3 comments · 2 reactions · Opened Sep 10, 2025
Validate provided repositories are publicly reachable (PGA golf server's github link is wrong) Open

enhancement tech requirements work

modelcontextprotocol/registry#395 · 8 comments · 1 assignee · Opened Sep 9, 2025
Create envelope structure for server.json with versioning and servers list Open

Difficulty 4/5 3-5 days Newbie friendliness 35/100

modelcontextprotocol/registry#301 · 4 comments · Opened Aug 26, 2025
Pingback from subregistries with extension data Open

api enhancement not go-live blocker product requirements work

Difficulty 5/5 Over a week Newbie friendliness 25/100

modelcontextprotocol/registry#292 · 3 comments · 1 reaction · Opened Aug 21, 2025
Allow engine or runtime version to be expressed for local MCP servers Open

enhancement not go-live blocker server.json v1

Difficulty 5/5 Over a week Newbie friendliness 25/100

modelcontextprotocol/registry#125 · 7 comments · 1 reaction · Opened Jun 5, 2025
Support an array of commands (multiple commands) to start an MCP server instead of just one Open

enhancement not go-live blocker server.json v1

Difficulty 5/5 Over a week Newbie friendliness 45/100

modelcontextprotocol/registry#124 · 14 comments · Opened Jun 4, 2025
Automatically remove server.json entries referencing invalid packages Open

implementation work not go-live blocker

Difficulty 4/5 3-5 days Newbie friendliness 35/100

modelcontextprotocol/registry#93 · 4 comments · Opened May 27, 2025
Include ServerCapabilities in server.json Open

not go-live blocker v1

Difficulty 3/5 1-2 days Newbie friendliness 55/100

modelcontextprotocol/registry#84 · 5 comments · 1 reaction · Opened May 27, 2025
Incorporate MCP clients into the official MCP registry Open

not go-live blocker

Difficulty 5/5 Over a week Newbie friendliness 25/100

modelcontextprotocol/registry#83 · 1 reaction · Opened May 27, 2025
Preventing tool poisoning: save signatures of possible tool calls Open

not go-live blocker

modelcontextprotocol/registry#82 · 19 comments · 1 reaction · 1 assignee · Opened May 27, 2025
Entry Criteria Open

enhancement not go-live blocker

Difficulty 5/5 Over a week Newbie friendliness 25/100

modelcontextprotocol/registry#31 · 3 comments · 2 reactions · Opened May 9, 2025
"Publisher" data in official metaregistry Open

enhancement not go-live blocker

modelcontextprotocol/registry#29 · 20 comments · 1 assignee · Opened May 9, 2025
OAuth Config (Optional) for Remotes Open

not go-live blocker product requirements work

Difficulty 5/5 Over a week Newbie friendliness 35/100

modelcontextprotocol/registry#25 · 16 comments · 5 reactions · Opened May 9, 2025

modelcontextprotocol/registry

Get new issues in your inbox