Deps.rs

nambok / mentedb-mcp

[![dependency status](https://deps.rs/repo/github/nambok/mentedb-mcp/status.svg)](https://deps.rs/repo/github/nambok/mentedb-mcp)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate mentedb-mcp

Dependencies

(24 total, 11 outdated, 1 insecure)

CrateRequiredLatestStatus
 rmcp ⚠️~1.33.5.1insecure
 anyhow^11.0.104up to date
 tokio^11.53.3up to date
 serde^11.0.229up to date
 serde_json^11.0.154up to date
 clap^44.6.7up to date
 tracing^0.10.1.44up to date
 tracing-subscriber^0.30.3.23up to date
 tracing-appender^0.20.2.5up to date
 uuid^11.28.0up to date
 regex^11.13.1up to date
 schemars^11.2.3up to date
 axum^0.70.8.9out of date
 open^55.4.4up to date
 reqwest^0.120.13.5out of date
 mentedb^0.34.00.41.0out of date
 mentedb-core^0.34.00.41.0out of date
 mentedb-graph^0.34.00.41.0out of date
 mentedb-cognitive^0.34.00.41.0out of date
 mentedb-context^0.34.00.41.0out of date
 mentedb-embedding^0.34.00.41.0out of date
 mentedb-extraction^0.34.00.41.0out of date
 mentedb-consolidation^0.34.00.41.0out of date
 openssl^0.100.10.81up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^33.27.0up to date

Security Vulnerabilities

rmcp: DNS rebinding vulnerability in rmcp Streamable HTTP server transport

RUSTSEC-2026-0189

Prior to version 1.4.0, the rmcp crate's Streamable HTTP server transport did not validate the incoming Host header.

This allowed a malicious public website, via a DNS rebinding attack, to send requests to an MCP server running on the victim's loopback or private-network interface.

An attacker who convinced a victim to visit a malicious page could enumerate and invoke tools exposed by a locally running rmcp-based MCP server, read resources and prompts, and trigger side effects limited by the tools exposed by that server.

Non-HTTP transports such as stdio and child-process transports are not affected.

Patches

The issue was fixed in rmcp 1.4.0 by adding default loopback-only host allowlist validation for the Streamable HTTP server transport. Incoming HTTP requests now validate the Host header and return HTTP 403 when the host is not allowed.

Users should upgrade to rmcp >= 1.4.0.

Workarounds

If upgrading is not possible, place the MCP server behind a reverse proxy configured to reject requests whose Host header is not one of the expected hostnames. Do not bind the MCP server to 0.0.0.0 without such validation.