Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

ai.adeu/adeu

NPM · @ADEU/MCP-SERVER · SCANNED AUG 3

Automated DOCX Redlining Engine

Available components

+33 this week 76 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree. 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 9 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • 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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @adeu/mcp-server

# add to Claude Code
claude mcp add ai-adeu-adeu -- npx -y @adeu/mcp-server
# add to Codex CLI
codex mcp add ai-adeu-adeu -- npx -y @adeu/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-adeu-adeu": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@adeu/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-adeu-adeu --command npx --arg -y --arg @adeu/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  ai-adeu-adeu:
    command: "npx"
    args: ["-y", "@adeu/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "ai-adeu-adeu": {
      "command": "npx",
      "args": [
        "-y",
        "@adeu/mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +42
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Known CVEs: unverified → partial security
    • The attested source repository moved: dealfluence/adeu security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 1 Aug 26 +8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 29 Jul 26 +19
    • Tool coverage: unverified → 100 functional
  • 28 Jul 26 −19
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 43

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@adeu/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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
Discovery method:
attestation_endpoint
Dependencies 99 packages

99 packages in the resolved dependency tree · 97 deprecated · 31 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 9 exposed · ~1,318 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
docx_pathstringyesAbsolute path to the DOCX file.
output_pathstringOptional 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.

NameTypeReqDescription
attachment_pathsarray
body_markdownstringyes
reply_to_email_idstring
subjectstring
to_recipientsarray

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.

NameTypeReqDescription
compare_cleanbooleanIf True, compares 'Accepted' state. If False, compares raw text.
modified_pathstringyesAbsolute path to the modified DOCX file.
original_pathstringyesAbsolute 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.

NameTypeReqDescription
accept_allbooleanIf true, auto-accepts all unresolved track changes before finalizing.
authorstringReplace all remaining markup authorship with this name.
export_pdfbooleanIgnored in this environment.
file_pathstringyesAbsolute path to the DOCX file.
output_pathstringOptional output path.
passwordstringIgnored in this environment.
protection_modestringNative OOXML document locking. encrypt falls back to read_only in this environment.
sanitize_modestringfull 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.

NameTypeReqDescription
author_namestringyesName to appear in Track Changes (e.g., 'Reviewer AI').
changesarrayyesList of changes to apply. Each change must specify 'type'.
original_docx_pathstringyesAbsolute path to the source file.
output_pathstringOptional 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.

NameTypeReqDescription
clean_viewbooleanIf False (default), returns the 'Raw' text with inline CriticMarkup. If True, returns 'Accepted' text.
file_pathstringyesAbsolute path to the DOCX file.
modestring'full' returns body content. 'outline' returns a structural heading map. 'appendix' returns defined terms.
outline_max_levelnumberFor mode='outline' only: cap on heading depth.
outline_verbosebooleanFor mode='outline' only: includes metadata.
pagenumberPage 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.

NameTypeReqDescription
attachment_namestring
days_agonumber
email_idstring
folderstring
has_attachmentsboolean
is_unreadboolean
limitnumber
offsetnumber
senderstring
subjectstring
working_directorystring

No output schema declared.

No examples provided.