Word Document Operations (ceilf6/word-mcp-agent) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 37 tools. No publisher has claimed this listing.

C
Caution
74/100

Word Document Operations

Comprehensive CRUD operations and document manipulation for Microsoft Word files with table management, formatting controls, and merge capabilities.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ceilf6

Source: PulseMCP

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configWORDMCP_DIR
configWORDMCP_MAX_SIZE
configWORDMCP_LOG_LEVEL
configWORDMCP_LOG_DIR
configWORDMCP_CACHE_SIZE
configWORDMCP_MAX_DEPTH
configWORDMCP_MAX_IMAGE_SIZE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

37/37 tools missing one or more hints — plan_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tool_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_document (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +34 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — delete_document deletes at line 566 (file_path.unlink()); delete_word_document deletes at line 328 (os.remove(file_path))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

17/37 tools referenced in tests (46%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ceilf6/word-mcp-agent?variant=verified)](https://m8ven.ai/mcp/ceilf6/word-mcp-agent)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 69dd822f0aa1c01831bee19503b319737520f84a
code hash: 3c9f9c447977d1ed5a9392c2296330fb6e262c8783820f0294e5606e548e159b
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client