Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
fix(deps): bump rmcp to 2.x (2.2.0) for MCP transport security advisories
AkitaOnRails7ac58e6a63ea
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 08a74e62..be02aff5 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0## [Unreleased]+### Security+- Bumped `rmcp` to 2.x (2.2.0), resolving three MCP transport advisories:+ GHSA-9pj6-vhgr-3mwh (unauthenticated Streamable-HTTP session-table leak /+ DoS), GHSA-33f5-2c5q-wgwj (missing OAuth resource-field validation), and+ GHSA-9g45-5xwm-f3wc (custom headers leaking to cross-origin redirect+ targets). Behavior-preserving: the only source change is the+ `rmcp::model::Content` → `ContentBlock` rename (imported under the prior+ name), the feature set is unchanged, and the 23-tool MCP surface is+ unaffected. (#794)+## [2.3.2] - 2026-09-20### Changeddiff --git a/Cargo.lock b/Cargo.lockindex 25bd2249..826da750 100644--- a/Cargo.lock+++ b/Cargo.lock@@ -3219,9 +3219,9 @@ dependencies = [[[package]]name = "rmcp"-version = "1.7.0"+version = "2.2.0"source = "registry+https://github.com/rust-lang/crates.io-index"-checksum = "0810a9f717d9828f475fe1f629f4c305c8464b7f496c3a854b58d29e65f4058e"+checksum = "14db48ee17a9ba61810ab1a9c1beb7d06d8136ae39ac25a1137f10d357af01af"dependencies = ["async-trait","base64 0.22.1",@@ -3251,9 +3251,9 @@ dependencies = [[[package]]name = "rmcp-macros"-version = "1.7.0"+version = "2.2.0"source = "registry+https://github.com/rust-lang/crates.io-index"-checksum = "6aefac48c364756e97f04c0401ba3231e8607882c7c1d92da0437dc16307904d"+checksum = "783d787bf21813b285f13019adc49e11af501c658890c1e519f31f937c68b7e3"dependencies = ["darling 0.23.0","proc-macro2",@@ -3764,9 +3764,9 @@ dependencies = [[[package]]name = "sse-stream"-version = "0.2.3"+version = "0.2.6"source = "registry+https://github.com/rust-lang/crates.io-index"-checksum = "f3962b63f038885f15bce2c6e02c0e7925c072f1ac86bb60fd44c5c6b762fb72"+checksum = "c25ac7aff0abd1dbc474536e40416e1102c7dd9bfba0b9861c6d357f835dcfb4"dependencies = ["bytes","futures-util",diff --git a/Cargo.toml b/Cargo.tomlindex 849d66a6..23a690f7 100644--- a/Cargo.toml+++ b/Cargo.toml@@ -136,7 +136,7 @@ winapi-util = "0.1"# `aws_lc_rs`, which is exactly the C/JNI toolchain the bridge avoids by using# rmcp's `reqwest-tls-no-provider`. `ring` is already in the lockfile via reqwest 0.12.rustls = { version = "0.23", default-features = false, features = ["ring", "logging", "std", "tls12"] }-rmcp = { version = "1.7", features = ["server", "macros", "transport-io", "transport-streamable-http-server", "schemars"] }+rmcp = { version = "2.1", features = ["server", "macros", "transport-io", "transport-streamable-http-server", "schemars"] }schemars = "1"axum = "0.8"# Same `http` 1.x rmcp/axum use, so handlers can read the injecteddiff --git a/crates/ai-memory-cli/src/commands/mcp_bridge.rs b/crates/ai-memory-cli/src/commands/mcp_bridge.rsindex cb0d6235..1958c7c7 100644--- a/crates/ai-memory-cli/src/commands/mcp_bridge.rs+++ b/crates/ai-memory-cli/src/commands/mcp_bridge.rs@@ -198,7 +198,7 @@ mod tests {use std::sync::{Arc, Mutex};use axum::Router;- use rmcp::model::{Content, ServerCapabilities, Tool};+ use rmcp::model::{ContentBlock as Content, ServerCapabilities, Tool};use rmcp::transport::streamable_http_server::session::local::LocalSessionManager;use rmcp::transport::streamable_http_server::{StreamableHttpServerConfig, StreamableHttpService,diff --git a/crates/ai-memory-mcp/src/server.rs b/crates/ai-memory-mcp/src/server.rsindex ec5c5457..e2681465 100644--- a/crates/ai-memory-mcp/src/server.rs+++ b/crates/ai-memory-mcp/src/server.rs@@ -24,8 +24,8 @@ use ai_memory_wiki::{Wiki, WikiError, WritePageRequest};use rmcp::handler::server::router::tool::ToolRouter;use rmcp::handler::server::wrapper::Parameters;use rmcp::model::{- CallToolResult, Content, Implementation, ListToolsResult, PaginatedRequestParams,- ProtocolVersion, ServerCapabilities, ServerInfo, Tool,+ CallToolResult, ContentBlock as Content, Implementation, ListToolsResult,+ PaginatedRequestParams, ProtocolVersion, ServerCapabilities, ServerInfo, Tool,};use rmcp::service::RequestContext;use rmcp::{