Today in MCP — 2026-10-02

MCP Server Releases

Three MCP-related projects shipped releases on October 1, 2026:

• github/github-mcp-server v1.13.0 — GitHub's official MCP server, released at 19:11 UTC.
• czlonkowski/n8n-mcp v2.91.0 — Updated the underlying n8n version to 2.41.x; released at 18:05 UTC.
• n8n-io/n8n n8n@2.41.5 — Stable release of the workflow automation platform (mcp-client, mcp-server topics); released at 08:05 UTC.

n8n-MCP Runtime Bugs

Two bugs filed against czlonkowski/n8n-mcp today highlight operational pain points:

• n8n_health_check mandatory npm call — The health check unconditionally calls registry.npmjs.org with a 5-second timeout and returns upToDate: true even on failure, masking outages in air-gapped environments.
• better-sqlite3 crash on Node 24.19+ — A V8 regression in Node.js ≥24.19 causes native addon aborts during garbage collection of prepared statements, affecting n8n-mcp deployments on newer Node versions.

MCP Session & Protocol Bugs

• ruby_llm MCP session loss with Faraday 1.x — RubyLLM::MCP::HTTP::Stream fails to preserve session IDs when using Faraday 1.10.0+, because Faraday 1 drops the environment parameter in the on_data callback. Subsequent requests lose authentication headers and fail. Also breaks CI on all Ruby 3.x jobs.

Active MCP Ecosystem Repos

The GitHub topic:mcp search (2,117 repos total) shows heavy activity at the top end. The three highest-starred repos that pushed in the last 24 hours:

Awesome-MCP Registry

No new servers were merged into punkpeye/awesome-mcp-servers in the past 24 hours. Two PRs remain open but unmerged (#14643, #10927).

Summary: A quiet day for new MCP server listings but active on the release and bug-report fronts. The n8n/MCP corner saw a coordinated release day (n8n 2.41.5 + n8n-mcp 2.91.0) followed immediately by two runtime regression reports. The ruby_llm Faraday compatibility bug is the most broadly impactful protocol-level issue.