Today in MCP — 2026-07-02

Active MCP Repositories

Three MCP-tagged repositories had pushes in the past 24 hours, led by projects with real production traffic:

• firecrawl/firecrawl-mcp-server (6,781 ★) — Firecrawl's web-scraping MCP server continued active development, last pushed 01:24 UTC.
• homeassistant-ai/ha-mcp (3,758 ★) — Home Assistant's MCP bridge is in rapid iteration, with pushes at 04:25 UTC.
• the-open-agent/openagent (5,321 ★) — Open agent platform with MCP integration, pushed at 03:44 UTC.

The punkpeye/awesome-mcp-servers directory had 0 new servers merged — a quiet day for new listings.

MCP-Enabled Releases

Three packages shipped within the window:

• homeassistant-ai/ha-mcp v7.9.0.dev751 — Automated dev build released 04:25 UTC, part of a rapid 7.9.0 pre-release series.
• the-open-agent/openagent v2.69.0 — Latest stable cut of the agent platform at 03:54 UTC, following three patch releases since yesterday.
• spencerbeggs/vitest-agent @vitest-agent/mcp@1.3.2 — Enhanced test_history output with modulePath; corrected recovered test detection logic. Released ~00:40 UTC as part of a coordinated multi-package release.

MCP Server Spec & Implementation Issues

Protocol-level correctness issues surfaced from the VaultPilot project:

• mcp_server: tokio::select! bias allows one extra request after shutdown — A race condition in the Rust MCP server lets one additional request through after shutdown is signaled due to tokio::select! branch ordering.
• mcp_server: ping accepted before initialization handshake — Server accepts ping messages before the MCP init handshake completes, a spec violation; reported by ryanloee.
• Evaluate optional OAuth integration with mcp-runtime-go — Feature discussion on whether to bolt OAuth onto the mcp-runtime-go instance for the hugo-public-mcp project.

Summary

A routine day in MCP-land: the awesome-mcp-servers directory saw no new additions, but three actively maintained MCP implementations shipped releases and two spec-compliance bugs were filed against a Rust MCP server implementation. The push toward a stateless MCP v2 (spec RC slated for 2026-07-28) is likely influencing the protocol-correctness issues surfacing now.