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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

mangaba_ai

Framework profissional de orquestracao multi-agente em Python: crews, flows orientados a eventos, ReAct, RAG, memoria, MCP/A2A e multi-provider LLM

→ Mangaba-ai/mangaba_ai· listed on github_topic

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

Mangaba-ai

Source: github_topic

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
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 10 credentials: SERPER_API_KEY, API_KEY, GOOGLE_API_KEY, GEMINI_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, HUGGINGFACE_API_KEY, HUGGINGFACE_TOKEN, HF_TOKEN, HUGGINGFACEHUB_API_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.
🔐 secretSERPER_API_KEY
configLLM_PROVIDER
🔐 secretAPI_KEY
configMODEL_NAME
configLOG_LEVEL
configAI_PROVIDER
configPROVIDER
configMODEL
🔐 secretGOOGLE_API_KEY
🔐 secretGEMINI_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretANTHROPIC_API_KEY
🔐 secretHUGGINGFACE_API_KEY
🔐 secretHUGGINGFACE_TOKEN
🔐 secretHF_TOKEN
🔐 secretHUGGINGFACEHUB_API_TOKEN
configMODEL_TEMPERATURE
configMAX_OUTPUT_TOKENS
configMAX_TOKENS
configSYSTEM_PROMPT
configUSE_MCP
configUSE_A2A
configMLFLOW_TRACKING_URI
configMLFLOW_EXPERIMENT_NAME
configOTEL_SERVICE_NAME
configOTEL_EXPORTER_OTLP_TRACES_ENDPOINT
configPHOENIX_PROJECT_NAME
configPHOENIX_COLLECTOR_ENDPOINT
configMANGABA_VECTORSTORE_URL
configMANGABA_REDIS_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

22/22 tools missing one or more hints — mcp (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); codeinterpreter (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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 test coverage

Only 3/22 tools referenced in tests (14%)

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 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/mangaba-ai/mangaba_ai)](https://m8ven.ai/mcp/mangaba-ai/mangaba_ai)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6a148ad68e32f54d92e57608ef92a6e65a4f6ec7
code hash: 0765ca3e5a3432c538fd9f988ddc4389c04fecf82869312830cb92948dc64760
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