Vexa (Vexa-ai/vexa) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
—
Not scored

Vexa

Open-source meeting bot API with MCP server. Search, retrieve, and analyze meeting transcripts from Google Meet, Zoom, and Microsoft Teams directly from your AI tools.

→ Vexa-ai/vexa· listed on glama

How we 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

Vexa-ai

Source: Glama · also listed on 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

Glamanot scored hereGitHub

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// key findings
🚨
Secret credentials may flow to a network call
6 flows detected: VEXA_ADMIN_API_KEY, VEXA_INTERNAL_API_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 8 credentials: GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET, NEXTAUTH_SECRET, TRANSCRIPTION_SERVICE_TOKEN, VEXA_ADMIN_API_KEY, VEXA_API_KEY, VEXA_BOT_API_KEY, VEXA_INTERNAL_API_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalnext@15.5.21GHSA-2xp9-vwfh-vxw4

Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

criticalnext@15.5.21GHSA-p293-qw3h-jr36

Next.js: Unauthenticated Remote Code Execution on windows-hosted servers

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configAGENT_API_URLAll upstreams resolve to (default http://127.0.0.1:18100).
configGATEWAY_URL
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configHOST
configMICROSOFT_CLIENT_ID
🔐 secretMICROSOFT_CLIENT_SECRET
configMICROSOFT_TENANT_ID
🔐 secretNEXTAUTH_SECRET
configNEXTAUTH_URL
configOPS_STATUS_FILE
configTERMINAL_URL
configTRANSCRIPTION_MODEL
🔐 secretTRANSCRIPTION_SERVICE_TOKEN
configTRANSCRIPTION_SERVICE_URL
🔐 secretVEXA_ADMIN_API_KEYroutes call admin-api with the server's (admin tier, like the login flow) and
configVEXA_ADMIN_API_URL
configVEXA_ADMIN_EMAILS
🔐 secretVEXA_API_KEY
configVEXA_API_URL
configVEXA_AUTH_COOKIE_NAME
🔐 secretVEXA_BOT_API_KEY
🔐 secretVEXA_INTERNAL_API_SECRET
configVEXA_JITSI_HOSTS
configVEXA_TEAMS_PIPELINE_BACKEND
configVEXA_TEAMS_PIPELINE_REFERENCE
configVEXA_TERMINAL_LOGIN_TOKEN_CAPsign-in the terminal prunes a user's oldest terminal-login tokens beyond
configVEXA_USER_INFO_COOKIE_NAME
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_DEFAULT_BOT_NAME
deployNEXT_PUBLIC_GA_MEASUREMENT_ID
deployNEXT_PUBLIC_TERMINAL_MODE
deployPORT
// quality suggestions

Tools detected

No tools extracted — insufficient content to verify at Tier 2

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Secrets not logged

3 secret values sent to warn/info

Redact or omit secret values from log output.

Production dependencies are patched

2 critical, 0 high severity in production deps — next@15.5.21 (critical), next@15.5.21 (critical)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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/vexa-ai/vexa)](https://m8ven.ai/mcp/vexa-ai/vexa)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 59e2c413a53479125b70b712ade12ab470d55512
code hash: 622a14529bb36f4cdbde2c680df8d6e49f4537c813d517e40fe791f28fc7307d
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