Skip to content

Epistates/TurboMCP

v3.0.11 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 1mo MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

mcp mcp-client mcp-sdk mcp-server mcp-servers rust

Summary

AI summary

Added RequestContext::notify_client(), Client::trigger_tool_list_changed(), Client::has_tool_list_changed_handler(), and HandlerRegistry::has_tool_list_changed_handler() methods.

Full changelog

[3.0.11] - 2026-04-02

Added

  • RequestContext::notify_client() — New method on the server-side request context for sending JSON-RPC notifications to connected clients. Enables server handlers to push notifications/tools/list_changed, progress events, and other fire-and-forget messages over bidirectional transports (channel, WebSocket, SSE). Accepts impl AsRef<str> for ergonomic method names.

  • Client::trigger_tool_list_changed() — Programmatically invokes the registered ToolListChangedHandler, returning HandlerResult<()> so callers can observe failures. Designed for testing and external notification integration scenarios.

  • Client::has_tool_list_changed_handler() — Check whether a tool list changed handler is registered, consistent with existing has_roots_handler(), has_elicitation_handler(), etc.

  • HandlerRegistry::has_tool_list_changed_handler() — Proper has_* predicate on the registry, avoiding unnecessary Arc clone through get_*().is_some().

Full Changelog: https://github.com/Epistates/turbomcp/compare/v3.0.10...v3.0.11

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Epistates/TurboMCP

Get notified when new releases ship.

Sign up free

About Epistates/TurboMCP

TurboMCP SDK: Enterprise MCP SDK in Rust

All releases →

Beta — feedback welcome: [email protected]