ai-stack (hannovdm/ai-stack) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Emerging

74/100

10 days ago

ai-stack

Item: ai-stack
Rating: 74
Author: M8ven

Local AI stack configuration, orchestration and workspace

→ hannovdm/ai-stack · listed on github_code

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 push why connect →

Who stands behind it

hannovdm

Source: github_code

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

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

// key findings

🚨

Secret credentials may flow to a network call

3 flows detected: BRAVE_SEARCH_API_KEY, LITELLM_API_KEY, LANGFUSE_PUBLIC_KEY. We can’t prove the destination matches the brand the credential belongs to.

🔐

You'll be asked for 4 credentials: MCP_GATEWAY_API_KEY, BRAVE_SEARCH_API_KEY, CRAWL4AI_API_TOKEN, LITELLM_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.

configARTIFACTS_ROOT

configSEARCH_RETRIEVAL_URL

🔐 secretMCP_GATEWAY_API_KEY

configSEARCH_APPROVAL_TTL_SECONDS

configBGE_RERANKER_MODEL

configBGE_RERANKER_MAX_LENGTH

configBGE_RERANKER_BATCH_SIZE

configBGE_RERANKER_DEVICE

🔐 secretBRAVE_SEARCH_API_KEYExport variables such as from the local env file

configCRAWL4AI_URL

🔐 secretCRAWL4AI_API_TOKEN

configRERANKER_URL

configRETRIEVAL_TIMEOUT_SECONDS

configMAX_PAGE_CHARACTERS

configCHUNK_CHARACTERS

configCHUNK_OVERLAP_CHARACTERS

configMAX_RERANK_CANDIDATES

configAPI_PORT

configUI_PORT

configDEPLOYMENT

configMODEL_ROOT

configCACHE_DIR

configCONFIG_DIR

configLITELLM_BASE_URL

🔐 secretLITELLM_API_KEY"headers": { "Authorization": "Bearer <>" }

configPOLICIES_DIR

configPOLICY_MODEL

configPOLL_INTERVAL

configPOLICY_EVAL_URL

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

// quality suggestions

Dependencies

3 dependencies, 1 flagged: playwright

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

6/6 tools missing one or more hints — web_research (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); speckit_run_full (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); speckit_specify (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (workspace/bge-reranker/server.py:54)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dependency freshness

1/2 production deps stale: nvm@2024-05-31 (2.2y)

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/hannovdm-ai-stack-08nhwu)](https://m8ven.ai/mcp/hannovdm-ai-stack-08nhwu)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: aaa2c43e6f616ad2bccda1cf582c2d3270b099bf

code hash: 557c90c47576a0a8a12a953d6c4cf56aa352e3096e43fd7a0025e97bf019e2d5

verified: 8/19/2026, 9:29:58 AM

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