camel (camel-ai/camel) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
8 days ago

camel

🐫 CAMEL: The first and the best multi-agent framework. Finding the Scaling Law of Agents. https://www.camel-ai.org

→ camel-ai/camel· listed on github_code

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

camel-ai

Source: github_code

Maintenance & responsiveness
as of 2026-08-19
Issue response: median 1h
Issues closed (90d): 36 · 473 open
Releases (90d): 1
Contributor retention: 5/19 stayed · 36 active
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
4 flows detected: TWITTER_CONSUMER_KEY, WECHAT_APP_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 50 credentials: AGENTOPS_API_KEY, SMITHERY_API_KEY, ACI_API_KEY, MINIMAX_API_KEY, ASKNEWS_CLIENT_SECRET, BOHRIUM_API_KEY, DAPPIER_API_KEY, DATACOMMONS_API_KEY, GITHUB_ACCESS_TOKEN, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, GOOGLE_API_KEY, XAI_API_KEY, OPENAI_API_KEY, EMAIL_PASSWORD, JINA_API_KEY, KLAVIS_API_KEY, LARK_APP_SECRET, LINKEDIN_ACCESS_TOKEN, MESHY_API_KEY, MICROSOFT_CLIENT_SECRET, NOTION_TOKEN, OPENBB_TOKEN, PLIVO_AUTH_TOKEN, PEXELS_API_KEY, REDDIT_CLIENT_SECRET, RESEND_API_KEY, SERPER_API_KEY, LINKUP_API_KEY, BRAVE_API_KEY, TAVILY_API_KEY, BOCHA_API_KEY, EXA_API_KEY, TONGXIAO_API_KEY, METASO_API_KEY, SERPAPI_KEY, QUERIT_API_KEY, PERPLEXITY_API_KEY, SLACK_BOT_TOKEN, STRIPE_API_KEY, TWELVELABS_API_KEY, TWITTER_CONSUMER_KEY, TWITTER_CONSUMER_SECRET, TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_TOKEN_SECRET, OPENWEATHERMAP_API_KEY, WECHAT_APP_SECRET, WHATSAPP_ACCESS_TOKEN, ZAPIER_NLA_API_KEY, TELEGRAM_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.
configMCP_CONNECT_CONCURRENCY
🔐 secretAGENTOPS_API_KEY
🔐 secretSMITHERY_API_KEY
🔐 secretACI_API_KEY
🔐 secretMINIMAX_API_KEY
configMINIMAX_API_HOST
configMINIMAX_MCP_BASE_PATH
configACI_BASE_URL
configASKNEWS_CLIENT_ID
🔐 secretASKNEWS_CLIENT_SECRET
🔐 secretBOHRIUM_API_KEY
configCAMEL_RUNTIME
configCAMEL_WORKDIR
🔐 secretDAPPIER_API_KEY
🔐 secretDATACOMMONS_API_KEY
🔐 secretGITHUB_ACCESS_TOKEN
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
🔐 secretGOOGLE_REFRESH_TOKEN
🔐 secretGOOGLE_API_KEY
🔐 secretXAI_API_KEY
🔐 secretOPENAI_API_KEY
configOPENAI_API_BASE_URL
configIMAP_SERVER
configEMAIL_USERNAME
🔐 secretEMAIL_PASSWORD
🔐 secretJINA_API_KEY
🔐 secretKLAVIS_API_KEY
configLARK_APP_ID
🔐 secretLARK_APP_SECRET
🔐 secretLINKEDIN_ACCESS_TOKEN
🔐 secretMESHY_API_KEY
configCAMEL_OUTLOOK_DEBUG_TOKEN_CLAIMS
configMICROSOFT_TENANT_ID
configMICROSOFT_CLIENT_ID
🔐 secretMICROSOFT_CLIENT_SECRET
🔐 secretNOTION_TOKEN
🔐 secretOPENBB_TOKEN
configPLIVO_AUTH_ID
🔐 secretPLIVO_AUTH_TOKEN
🔐 secretPEXELS_API_KEY
configREDDIT_CLIENT_ID
🔐 secretREDDIT_CLIENT_SECRET
configREDDIT_USER_AGENT
🔐 secretRESEND_API_KEY
🔐 secretSERPER_API_KEY
🔐 secretLINKUP_API_KEY
🔐 secretBRAVE_API_KEY
configSEARCH_ENGINE_ID
🔐 secretTAVILY_API_KEY
🔐 secretBOCHA_API_KEY
🔐 secretEXA_API_KEY
🔐 secretTONGXIAO_API_KEY
🔐 secretMETASO_API_KEY
🔐 secretSERPAPI_KEY
🔐 secretQUERIT_API_KEY
🔐 secretPERPLEXITY_API_KEY
🔐 secretSLACK_BOT_TOKEN
🔐 secretSTRIPE_API_KEY
🔐 secretTWELVELABS_API_KEY
🔐 secretTWITTER_CONSUMER_KEY
🔐 secretTWITTER_CONSUMER_SECRET
🔐 secretTWITTER_ACCESS_TOKEN
🔐 secretTWITTER_ACCESS_TOKEN_SECRET
configGOOGLE_CLOUD_PROJECT
🔐 secretOPENWEATHERMAP_API_KEY
configWECHAT_APP_ID
🔐 secretWECHAT_APP_SECRET
🔐 secretWHATSAPP_ACCESS_TOKEN
configWHATSAPP_PHONE_NUMBER_ID
configWOLFRAMALPHA_APP_ID
🔐 secretZAPIER_NLA_API_KEY
configCAMEL_LOGGING_DISABLED
configCAMEL_LOGGING_LEVEL
configTRACEROOT_ENABLED
🔐 secretTELEGRAM_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySMTP_SERVER
// 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

17/17 tools missing one or more hints — step (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reset (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_output_language (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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

10/17 tools referenced in tests (59%)

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

Secrets stay with their owner

4 secrets sent to a request target we could not resolve (TWITTER_CONSUMER_KEY → dynamic, TWITTER_CONSUMER_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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/camel-ai/camel)](https://m8ven.ai/mcp/camel-ai/camel)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d198715162d219219e92f8fe24579420b4286744
code hash: fdd38255b96a51b0ca0d92268fbc78272540909cb332b93fa353cea7e12e6619
verified: 9/3/2026, 11:02:52 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