litellm (BerriAI/litellm) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 1 tool. No publisher has claimed this listing.

B
Warning
89/100
7 days ago

litellm

The fastest, litest AI Gateway. Rust core with Python SDK. Call 100+ LLM APIs in OpenAI (or native) format with cost tracking, guardrails, load balancing, and logging [Bedrock, Azure, OpenAI, Anthropic, OpenAI, VertexAI, vLLM, Nvidia NIM]

Warning. Serious findings were identified. Review the full report before connecting. 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

BerriAI

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 →

Install from

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

// key findings
🚨
Code appears obfuscated
121 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 8 credentials: ANTHROPIC_API_KEY, HF_TOKEN, HUGGINGFACE_API_KEY, OLLAMA_API_KEY, PROMPTLAYER_API_KEY, LITELLM_API_KEY, OPENAI_API_KEY, ACTIONS_ID_TOKEN_REQUEST_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.
🔐 secretANTHROPIC_API_KEY
🔐 secretHF_TOKEN
🔐 secretHUGGINGFACE_API_KEY
configDATABRICKS_API_BASE
🔐 secretOLLAMA_API_KEY
🔐 secretPROMPTLAYER_API_KEY
configLITELLM_PROXY_URL
🔐 secretLITELLM_API_KEY
configLITELLM_MODEL
configOPENAI_BASE_URL
configOPENAI_API_BASE
configOPENAI_ORGANIZATION
🔐 secretOPENAI_API_KEY
configLITELLM_AZURE_REALTIME_PROTOCOL
configLITELLM_OIDC_ALLOWED_CREDENTIAL_DIRS
configACTIONS_ID_TOKEN_REQUEST_URL
🔐 secretACTIONS_ID_TOKEN_REQUEST_TOKEN
configAZURE_FEDERATED_TOKEN_FILE
configMCP_JWT_ISSUER
configLITELLM_EXTERNAL_URL
configMCP_JWT_AUDIENCE
configMCP_JWT_TTL_SECONDS
configUSE_MCP
configJWT_ISSUER
configPROXY_BASE_URL
configSERVER_ROOT_PATH
configLITELLM_MCP_SERVER_NAME
configLITELLM_MCP_SERVER_DESCRIPTION
configMCP_TOOL_PREFIX_SEPARATOR
configLITELLM_USE_SHORT_MCP_TOOL_PREFIX
// 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

2/2 tools missing one or more hints — mcp_server_tool_call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); listmcptoolsrestapiresponseobject (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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 test coverage

1/2 tools referenced in tests (50%)

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

Readable source code

121 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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 Verified](https://m8ven.ai/badge/mcp/berriai/litellm?variant=verified)](https://m8ven.ai/mcp/berriai/litellm)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 92122086ecc9271640d284fe4e1db32bdfc205ff
code hash: 17e82196291a26e4d156abca3068eb8ce7776f7d002a80690e43c6ca9758620d
verified: 9/3/2026, 7:38:33 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