Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"adeu": {
"args": [
"--from",
"adeu",
"adeu-server"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
LLMs speak Markdown; Lawyers speak "Track Changes."
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@adeu/core' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
uv allows ZIP payload obfuscation through parsing differentials
## Impact In versions 0.8.5 and earlier of uv, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. This enabled two parser differentials against other Python package installers: 1. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. The attacker could choose which installer to target
uv is vulnerable to arbitrary file write through entry point names
### Impact In versions of uv prior to 0.11.15, when installing a distribution containing an entry point specification (under `console_scripts` or `gui_scripts`), uv would place the generated entry point according to the given name even if doing so resulted in a path outside of the environment's scripts directory. A malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's `PATH`. This could shadow or overwr
uv vulnerable to arbitrary file deletion through RECORD entries
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall. uv does not use the RECORD fi
PYSEC-2026-2295
A flaw was found in uv. This vulnerability allows an attacker to execute malicious code during package resolution or installation via specially crafted ZIP (Zipped Information Package) archives that exploit parsing differentials, requiring user interaction to install an attacker-controlled package.
uv has differential in tar extraction with PAX headers
### Impact In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers. The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518. In practice, the impact of this vulnerability is **low**:
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in writing
【Star-crossed coders unite!⭐️】Model Context Protocol (MCP) server implementation providing Google News search capabilities via SerpAPI, with automatic news categorization and multi-language support.
URL to LLM-ready markdown — plus per-page category, page_structure, and query-driven highlights.
AI prompt optimization for 58+ platforms across 7 categories with custom platforms
Model Context Protocol (MCP) Server to connect your AI with any MediaWiki
MCP Security Weekly
Get CVE alerts and security updates for ai.adeu/adeu and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
LLMs speak Markdown; reviewers speak "Track Changes."
Adeu is a docx ↔ LLM translator: a Model Context Protocol (MCP) server (Python and Node.js implementations) and accompanying SDKs that act as a Virtual DOM for Microsoft Word. It provides a two-way abstraction layer that lets AI agents freely edit document text without destroying the underlying formatting or complex DOCX XML.
While standard libraries like python-docx excel at generating documents from scratch, they fail at non-destructive redlining. Adeu solves this by translating .docx files into a token-efficient Markdown representation. This frees AI agents to focus entirely on document semantics instead of wasting tokens wrestling with OpenXML.
Adeu acts as an intelligent proxy, processing AI edits as safe, atomic transactions:
Built and maintained by the team at Adeu.
Adeu can be installed directly into AI assistants as an MCP server, used as a Claude Code plugin or Agent Skill, or used locally as a developer toolchain.
Adeu ships as a Claude Code plugin with a built-in agent skill that teaches Claude how to use the engine effectively. Inside Claude Code:
/plugin marketplace add dealfluence/adeu
/plugin install adeu-redlining@adeu-skills
For best results, also connect either the Node MCP server (npx -y @adeu/mcp-server) or the Python MCP server (uvx --from adeu adeu-server). The plugin works without an MCP server too — it falls back to driving the uvx adeu CLI via Bash.
Adeu's redlining skill follows the open Agent Skills specification and works with any compatible agent:
npx skills add dealfluence/adeu
The skill installs to your agent's skills directory and activates automatically when you ask Claude to redline, edit, or review a .docx file.
You can install Adeu directly into Claude Desktop using the official extension package:
Adeu.mcpb file from the GitHub Releases page.