beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & Serving
Personal
WatchlistCompare
?
Sign in
magic link · no password
LIVE──────── · ──:──:── UTCabout
beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & Serving
Personal
WatchlistCompare
?
Sign in
magic link · no password
Back to modelcontextprotocol/registry
[STATUS / STABLE]

Is modelcontextprotocol/registry still actively maintained? (May 2026)

Yes. modelcontextprotocol/registry is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 1.1/10.

What the signals say
  • Last commit8 days ago (May 14, 2026)
  • Contributors64
  • Stars6,820 (+28 in last 7 days)
  • Star delta (30d)+140 in last 30 days
  • Velocity score1.1/10 (stable)
What ‘stable’ means on beam

Stable means the repo’s velocity score has been consistent over the last 7 days — healthy maintenance signals, no momentum loss, no contributor drop-off. Full methodology →

Frequently asked

Is modelcontextprotocol/registry still actively maintained? (May 2026)

Yes. modelcontextprotocol/registry is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 1.1/10.

How is beam classifying modelcontextprotocol/registry?

Beam classifies modelcontextprotocol/registry as stable with a velocity score of 1.1/10. Beam fuses code activity, package adoption, sentiment, research citation, and production signals into a single 0–10 score; the classification thresholds are explained on /about.

When was the last commit to modelcontextprotocol/registry?

The most recent commit to modelcontextprotocol/registry was 8 days ago (May 14, 2026).

How can I track modelcontextprotocol/registry's status going forward?

Beam refreshes modelcontextprotocol/registry's velocity score and class daily. The live tool profile is at /tools/1257; the JSON API endpoint is /api/v1/tools/1257.

Full tool profile Methodology API
LIVE──────── · ──:──:── UTCabout