Enterprise-AI-Office (licat233/Enterprise-AI-Office) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Enterprise-AI-Office

A reusable, agent-readable blueprint for building a self-hosted Enterprise AI Office with knowledge, agents, RBAC, automation, workflows and enterprise tools.

→ licat233/Enterprise-AI-Office· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

licat233

Source: github_repo_search

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

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
🚨
Secret credentials may flow to a network call
1 flow detected: EAIO_EAO_ADMIN_WEKNORA_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: EAIO_EMAIL_CLIENT_PASSWORD, EAIO_EAO_ADMIN_WEKNORA_API_KEY, EAIO_TRUSTED_FORWARDER_TOKEN, FIRECRAWL_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configPLUGIN_EVAL_APPROVED_SKILL_ROOTS
configPLUGIN_EVAL_UPSTREAM_ROOT
configEAIO_EMAIL_ALLOWED_FOLDERS
configEAIO_EMAIL_IMAP_HOST
configEAIO_EMAIL_USERNAME
🔐 secretEAIO_EMAIL_CLIENT_PASSWORD
configARMOR_VAULT_ROOT
configEAIO_RUNTIME_ROOT
configEAIO_WHISPER_MODEL_CACHE
configEAIO_WHISPER_DETECTION_MODEL
configEAIO_WHISPER_MODEL
configEAIO_SENSEVOICE_MODEL
configEAIO_SENSEVOICE_VAD_MODEL
configEAIO_SENSEVOICE_BATCH_SECONDS
configEAIO_COMPANY_CONFIG
configEAIO_EAO_ADMIN_GROUP_ID
configEAIO_EAO_ADMIN_ASSISTANT_ID
configEAIO_EAO_ADMIN_WEKNORA_BASE_URL
🔐 secretEAIO_EAO_ADMIN_WEKNORA_API_KEY
configEAIO_EAO_ADMIN_KB_ID
configEAIO_EAO_ADMIN_HTTP_TIMEOUT_SECONDS
configEAIO_GOVERNANCE_URL
🔐 secretEAIO_TRUSTED_FORWARDER_TOKEN
configEAIO_OBSCURA_BIN
configEAIO_OBSCURA_STORAGE_DIR
configEAIO_OBSCURA_STORAGE_ROOT
configEAIO_CLOAKBROWSER_PYTHON
configEAIO_CLOAKBROWSER_WORKER
configEAIO_CLOAKBROWSER_STORAGE_DIR
configEAIO_CLOAKBROWSER_VERSION
🔐 secretFIRECRAWL_API_KEY
configFIRECRAWL_API_URL
// quality suggestions

Tool annotations

3/15 tools have annotations

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

All four hints declared on every tool

14/15 tools missing one or more hints — search_email (missing: destructiveHint, idempotentHint); get_email (missing: destructiveHint, idempotentHint); route_work_product (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (EAIO_EAO_ADMIN_WEKNORA_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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 3 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 Score](https://m8ven.ai/badge/mcp/licat233/enterprise-ai-office)](https://m8ven.ai/mcp/licat233/enterprise-ai-office)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2351f39ef0546928babd37684904199503ddcc06
code hash: 305ddb8a23517081756a311c5d290ec6a03cb2190e97ab1b927c7d6f029d5459
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