ai.adeu/adeu
NPM · @ADEU/MCP-SERVER · SCANNED SEP 20
Automated DOCX Redlining Engine
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dealfluence/adeu). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1318 tokens (~146/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ai.adeu/adeu MCP server?
ai.adeu/adeu runs locally as an npm package, launched with npx -y @adeu/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @adeu/mcp-server
claude mcp add ai-adeu-adeu -- npx -y @adeu/mcp-server
{
"mcpServers": {
"ai-adeu-adeu": {
"command": "npx",
"args": [
"-y",
"@adeu/mcp-server"
]
}
}
} {
"servers": {
"ai-adeu-adeu": {
"command": "npx",
"args": [
"-y",
"@adeu/mcp-server"
]
}
}
} codex mcp add ai-adeu-adeu -- npx -y @adeu/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-adeu-adeu": {
"type": "local",
"command": [
"npx",
"-y",
"@adeu/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add ai-adeu-adeu --command npx --arg -y --arg @adeu/mcp-server
mcp_servers:
ai-adeu-adeu:
command: "npx"
args: ["-y", "@adeu/mcp-server"] {
"McpServers": {
"ai-adeu-adeu": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@adeu/mcp-server"
]
}
}
} assistant mcp add ai-adeu-adeu -t stdio -c npx -a -y @adeu/mcp-server
{
"mcpServers": {
"ai-adeu-adeu": {
"command": "npx",
"args": [
"-y",
"@adeu/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@adeu/mcp-server@1.7.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dealfluence/adeu |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dealfluence/adeu/.github/workflows/release.yml@refs/tags/v1.7.1 |
| Rekor log index | 1553475028 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:deeabdb94282acaf62bf6b3838846f5fb1a95c1aeaf4f00778fc261e3521b965d1763d834017a2180a274af8548f708b04e59eddc6d4fb396b2c7492f |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_all_changes ~74
Accepts all tracked changes and removes all comments in a single operation, producing a finalized clean document. Use this when a document review is entirely complete and you want to clear all redlines.
| Name | Type | Req | Description |
|---|---|---|---|
| docx_path | string | yes | Absolute path to the DOCX file. |
| output_path | string | – | Optional output path. |
No output schema declared.
No examples provided.
create_email_draft ~91
Creates an email draft in the user's native draft box. Provide `reply_to_email_id` to reply, or `subject` and `to_recipients` for a new email.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_paths | array | – | – |
| body_markdown | string | yes | – |
| reply_to_email_id | string | – | – |
| subject | string | – | – |
| to_recipients | array | – | – |
No output schema declared.
No examples provided.
diff_docx_files ~90
Compares two DOCX files and returns a unified diff of their text content. Useful for analyzing differences between versions before editing.
| Name | Type | Req | Description |
|---|---|---|---|
| compare_clean | boolean | – | If True, compares 'Accepted' state. If False, compares raw text. |
| modified_path | string | yes | Absolute path to the modified DOCX file. |
| original_path | string | yes | Absolute path to the baseline DOCX file. |
No output schema declared.
No examples provided.
finalize_document ~190
Prepares a document for external distribution or e-signature. This tool combines metadata sanitization, document locking (protection), and markup resolution into a single step. NOTE: PDF export and AES encryption are disabled in this environment.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_all | boolean | – | If true, auto-accepts all unresolved track changes before finalizing. |
| author | string | – | Replace all remaining markup authorship with this name. |
| export_pdf | boolean | – | Ignored in this environment. |
| file_path | string | yes | Absolute path to the DOCX file. |
| output_path | string | – | Optional output path. |
| password | string | – | Ignored in this environment. |
| protection_mode | string | – | Native OOXML document locking. encrypt falls back to read_only in this environment. |
| sanitize_mode | string | – | full removes all markup, keep-markup redacts metadata but keeps comments/redlines. |
No output schema declared.
No examples provided.
login_to_adeu_cloud ~31
Logs the user into the Adeu Cloud backend. Securely opens a browser window for authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logout_of_adeu_cloud ~27
Logs out of the Adeu Cloud backend by clearing the local API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
process_document_batch ~391
Applies a batch of edits and review actions to a DOCX. All changes evaluate against the ORIGINAL document state — do not chain dependent edits within one batch (e.g. rename X to Y, then modify Y). Apply the rename first, then send a second batch. Each item in `changes` must specify a `type`: 1. 'modify': Search-and-replace. `target_text` must uniquely match — include surrounding context if the phrase is ambiguous. `new_text` supports Markdown: '# Heading 1' through '###### Heading 6', '**bold**', '_italic_', and '\n\n' to split into multiple paragraphs. Empty `new_text` deletes. Do NOT write CriticMarkup tags ({++, {--, {>>) manually — use the `comment` parameter for comments. 2. 'accept' / 'reject': Finalize or revert a tracked change by `target_id` (e.g. 'Chg:12'). 3. 'reply': Reply to a comment by `target_id` (e.g. 'Com:5') with `text`. 4. 'insert_row' / 'delete_row': Table edits. Disk mode only — not supported on Live Word canvas. ID VOLATILITY: 'Chg:N' and 'Com:N' shift between document states. Always call `read_docx` immediately before any accept/reject/reply — do not reuse IDs from earlier in the conversation. `author_name` is used for attribution on all tracked changes and comments, in both disk and Live Word modes.
| Name | Type | Req | Description |
|---|---|---|---|
| author_name | string | yes | Name to appear in Track Changes (e.g., 'Reviewer AI'). |
| changes | array | yes | List of changes to apply. Each change must specify 'type'. |
| original_docx_path | string | yes | Absolute path to the source file. |
| output_path | string | – | Optional output path. |
No output schema declared.
No examples provided.
read_docx ~288
Reads a DOCX file. Returns text with inline CriticMarkup for Tracked Changes and Comments: {++inserted++}, {--deleted--}, {==highlighted==}{>>comment<<}. Set clean_view=True for the finalized 'Accepted' text without markup. Modes: - 'full' (default): paginated body content. Use page=N to navigate. - 'outline': heading map only — start here for large docs to plan targeted reads. Defaults to L1-L2 headings; pass outline_max_level=3-6 to see deeper structure. - 'appendix': defined terms, anchors, and cross-reference targets. Consult before editing legal/technical docs to avoid breaking references.
| Name | Type | Req | Description |
|---|---|---|---|
| clean_view | boolean | – | If False (default), returns the 'Raw' text with inline CriticMarkup. If True, returns 'Accepted' text. |
| file_path | string | yes | Absolute path to the DOCX file. |
| mode | string | – | 'full' returns body content. 'outline' returns a structural heading map. 'appendix' returns defined terms. |
| outline_max_level | number | – | For mode='outline' only: cap on heading depth. |
| outline_verbose | boolean | – | For mode='outline' only: includes metadata. |
| page | number | – | Page number (1-indexed) for mode='full'. Defaults to 1. |
No output schema declared.
No examples provided.
search_and_fetch_emails ~136
Searches the user's live email inbox. By default, searches only the Inbox folder. Returns a list of lightweight previews. Call again with `email_id` to fetch the full body and download attachments.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_name | string | – | – |
| days_ago | number | – | – |
| email_id | string | – | – |
| folder | string | – | – |
| has_attachments | boolean | – | – |
| is_unread | boolean | – | – |
| limit | number | – | – |
| offset | number | – | – |
| sender | string | – | – |
| subject | string | – | – |
| working_directory | string | – | – |
No output schema declared.
No examples provided.
What is the ai.adeu/adeu MCP server?
ai.adeu/adeu is an MCP server listed in the public MCP registry as ai.adeu/adeu. Automated DOCX Redlining Engine. This page covers its npm package (@adeu/mcp-server).
Is the ai.adeu/adeu MCP server safe to use?
ai.adeu/adeu scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.adeu/adeu MCP server expose?
ai.adeu/adeu exposes 9 tools: read_docx, process_document_batch, accept_all_changes, diff_docx_files, finalize_document, and 4 more. Their descriptions and schemas cost roughly 1,318 tokens of context every time the server is loaded.
Is the ai.adeu/adeu MCP server still maintained?
ai.adeu/adeu is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ai.adeu/adeu MCP server under?
ai.adeu/adeu declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.