mcp-llm-router (groxaxo/mcp-llm-router) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

mcp-llm-router

An MCP server that routes LLM requests across multiple providers and orchestrates other MCP servers, with a focus on local privacy for embeddings and memory.

→ groxaxo/mcp-llm-router· listed on glama

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

groxaxo

Source: Glama

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

Glamanot scored here

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.
🔐
You'll be asked for 2 credentials: LLM_API_KEY, DEEPSEEK_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.
configMCP_ROUTER_MEMORY_DB
configROUTER_BRAIN_MODEL
configROUTER_BRAIN_BASE_URL
configROUTER_BRAIN_API_KEY_ENV
configROUTER_BRAIN_PROVIDER
configROUTER_BRAIN_MAX_TOKENS
configROUTER_BRAIN_TEMPERATURE
configROUTER_BRAIN_SYSTEM_PROMPT
configROUTER_BRAIN_REASONING_EFFORT
configMCP_JUDGE_ENABLE_TASKS
configOPENAI_BASE_URL
configOPENROUTER_BASE_URL
configDEEPINFRA_BASE_URL
configANTHROPIC_BASE_URL
configDEEPSEEK_BASE_URL
configEMBEDDINGS_BASE_URL
configEMBEDDINGS_MODEL
configEMBEDDINGS_PROVIDER
configEMBEDDINGS_PATH
configRERANK_BASE_URL
configRERANK_MODEL
configRERANK_PROVIDER
configRERANK_PATH
configRERANK_MODE
configEMBEDDINGS_API_KEY_ENV
configRERANK_API_KEY_ENV
configMCP_JUDGE_DATABASE_URL
🔐 secretLLM_API_KEYNote: the demo skips request_plan_approval because it requires user elicitation. Ensure DEEPSEEK_API_KEY (or ) is set and Ollama is running for embeddings.
configLLM_MODEL_NAME
configLLM_BASE_URL
🔐 secretDEEPSEEK_API_KEYNote: the demo skips request_plan_approval because it requires user elicitation. Ensure (or LLM_API_KEY) is set and Ollama is running for embeddings.
configMODEL
// 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

20/20 tools missing one or more hints — start_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); configure_brain (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_brain_config (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.).

Tool test coverage

Only 3/20 tools referenced in tests (15%)

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 4 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/groxaxo/mcp-llm-router)](https://m8ven.ai/mcp/groxaxo/mcp-llm-router)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b977ab42d9d00f05c18c1341c45bfe99b79e85f0
code hash: e8c60d173d34c97b556187c911a95c5d9b4767770fd850dc976127ac3c68e1e2
verified: 9/2/2026, 11:31:23 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