MCP Version Matrix Refresh — 2026-04-26

Re-audit since 2026-04-22. Refresh prompted by user request after pinning 21st-dev-magic@0.1.0.

Upstream deltas

PackageTierPrior auditNowΔ
@upstash/context7-mcpMED2.1.8 (2026-04-13)2.2.0 (2026-04-24)minor +1
tavily-mcpMED0.2.18 (2026-03-12)0.2.19 (2026-04-24)patch +1
fal-ai-mcpMED0.2.1 (2026-03-07)0.2.1unchanged
@21st-dev/magicHIGH0.1.0 (2025-12-23)0.1.0unchanged (now PINNED)
agentation-mcpHIGH1.2.0 (2026-02-15)1.2.0unchanged (disabled)
@modelcontextprotocol/server-sequential-thinkingLOW2025.12.182025.12.18unchanged
@modelcontextprotocol/server-memoryLOW2026.1.262026.1.26unchanged
notebooklm-mcp (user-level)LOW1.2.1 (2025-12-27)1.2.1unchanged

Recommendations status

#ActionStatus
1Pin HIGH-tier serversDONE 2026-04-26 (21st-dev-magic@0.1.0)
2Doctor check for HIGH-tier @latestDONE M117 #1462 (PR #1496)
3Document NotebookLM user-level depOPEN, low priority
490-day audit cadenceRECURRING, next 2026-07-25
5 (new)Re-evaluate agentation HIGH→MEDIUM after stabilizationOPEN, due 2026-07-25
Cadence note: 4 days between audits, 2 patch-level upstream changes, both auto-uptaken via @latest. The 90-day cadence is for tier reclassification (server going stale, hitting 1.0.0, losing maintainer activity), not version-tracking.

One-liner refresh script

for pkg in @upstash/context7-mcp tavily-mcp fal-ai-mcp @21st-dev/magic agentation-mcp \
           @modelcontextprotocol/server-sequential-thinking @modelcontextprotocol/server-memory \
           notebooklm-mcp; do
  v=$(npm view "$pkg" version 2>/dev/null)
  pub=$(npm view "$pkg" time.modified 2>/dev/null)
  printf "%-50s %-12s %s\n" "$pkg" "${v:-???}" "${pub:-unknown}"
done

References