AegisOps (emma-sue/AegisOps) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

C
Emerging
74/100
12 hours ago

AegisOps

AegisOps企业信息系统智能运维平台:自动巡检、Agent 故障排查、证据工单与审批处置。LangGraph · Deep Agents · MCP;附可复现实测记录。

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

emma-sue

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 9 credentials: DEMO_PASSWORD, DB_PASSWORD, CHAT_API_KEY, EMBEDDING_API_KEY, WORKER_TOKEN, POSTGRES_PASSWORD, LAB_DB_PASSWORD, LAB_CONTROL_TOKEN, LAB_READ_TOKEN
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.
configWEB_URL
configOPS_API_URL
🔐 secretDEMO_PASSWORD访问 http://127.0.0.1:5173,使用 ops-demo 登录。初始演示密码为 .env 中的 (示例值 demo-ops-2026)。
configAI_MODE默认 =fixture,无需模型密钥即可体验演示流程。已有 .env 时保留原配置。
🔐 secretDB_PASSWORD
configCHAT_MODELAI_MODE=live 时调用真实模型;缺失配置会报错
🔐 secretCHAT_API_KEYAI_MODE=live 时调用真实模型;缺失配置会报错
configEMBEDDING_MODEL默认关闭;启用后需匹配模型与维度
🔐 secretEMBEDDING_API_KEY默认关闭;启用后需匹配模型与维度
configEMBEDDING_ENABLED
🔐 secretWORKER_TOKEN
configCHECKPOINT_DATABASE_URL
🔐 secretPOSTGRES_PASSWORD
🔐 secretLAB_DB_PASSWORD
configLAB_DATABASE_URL
configLAB_API_URL
🔐 secretLAB_CONTROL_TOKEN
🔐 secretLAB_READ_TOKEN
configJAVA_HOME
configDEMO_AUTH
configSEED_KNOWLEDGE_IMPORT
configLAB_RENDER_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployREDIS_URL
// 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

14/14 tools missing one or more hints — read (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read (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.

Tool inputs are validated

12/14 tool handlers declare input schemas (86%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

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

Tool test coverage

5/14 tools referenced in tests (36%)

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 Score](https://m8ven.ai/badge/mcp/emma-sue/aegisops)](https://m8ven.ai/mcp/emma-sue/aegisops)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 211e0fddf193218ebcb31eb0f518591a2d60f127
code hash: 758b60a19c2ca73059d7f479dc712fc0bf232e9211bd090d95f4e0fb4eb67799
verified: 9/10/2026, 9:04:52 PM
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