F
Warning
12/100
1 day ago

Knowledge MCP

Exposes your Google Drive, Slack, GitHub, and Railway to MCP clients with semantic search, per-user permissions, and optional OAuth, allowing natural-language access to your private data and infrastructure.

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

⚡ 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

chanthr

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 →

Install from

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

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: OAUTH_GOOGLE_CLIENT_ID. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 16 credentials: DRIVE_CLIENT_SECRET, DRIVE_REFRESH_TOKEN, GITHUB_TOKEN, GOOGLE_OAUTH_CLIENT_SECRET, GOOGLE_OAUTH_REFRESH_TOKEN, GOOGLE_SERVICE_ACCOUNT_KEY, MATHPIX_APP_KEY, MCP_API_KEY, MCP_DEV_KEY, OAUTH_GOOGLE_CLIENT_SECRET, OAUTH_JWT_SECRET, OPENAI_API_KEY, QDRANT_API_KEY, SLACK_BOT_TOKEN, SLACK_TOKEN, SLACK_USER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high

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

highxlsx@0.18.5GHSA-4r6h-8v6p-xvw6

Prototype Pollution in sheetJS

highxlsx@0.18.5GHSA-5pgg-2g8v-p4x9

SheetJS Regular Expression Denial of Service (ReDoS)

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.
configACT_AS_ALLOWED_KEY_IDS
configACT_AS_CACHE_TTL_MS
configAUTH_CACHE_TTL_MS
configDRIVE_CLIENT_ID
🔐 secretDRIVE_CLIENT_SECRET
🔐 secretDRIVE_REFRESH_TOKEN
configDRIVE_SYNC_INTERVAL_MIN
configDRIVE_TIMEOUT_MS
configEMBED_BATCH
configEMBED_INDEX_RETRIES
configEMBED_QUERY_RETRIES
configEMBED_QUERY_TIMEOUT_MS
configEMBED_TIMEOUT_MS
configFOLDER_META_TTL_MS
configGITHUB_MCP_INSIDERS
configGITHUB_PAT
🔐 secretGITHUB_TOKEN
configGOOGLE_APPLICATION_CREDENTIALS
configGOOGLE_OAUTH_CLIENT_ID
🔐 secretGOOGLE_OAUTH_CLIENT_SECRET
🔐 secretGOOGLE_OAUTH_REFRESH_TOKEN
🔐 secretGOOGLE_SERVICE_ACCOUNT_KEY
configMATHPIX_APP_ID
🔐 secretMATHPIX_APP_KEY
🔐 secretMCP_API_KEY
configMCP_CONFIG_JSONConfig resolution order: (inline env) → MCP_CONFIG_PATH (file) →
configMCP_CONFIG_PATHConfig resolution order: MCP_CONFIG_JSON (inline env) → (file) →
configMCP_CORS_ORIGINS
🔐 secretMCP_DEV_KEY
configMCP_OAUTH_ISSUER
configMCP_RATE_LIMIT_FAIL_MAX
configMCP_RATE_LIMIT_MAX
configMCP_RATE_LIMIT_WINDOW_MS
configMCP_RESOURCE
configMCP_SESSION_IDLE_MS
configMCP_SESSION_MAX
configMCP_TRANSPORTnpm run dev # local (stdio or http per )
configOAUTH_ALLOWED_EMAILS
configOAUTH_ALLOWED_HD
configOAUTH_GOOGLE_CLIENT_ID
🔐 secretOAUTH_GOOGLE_CLIENT_SECRET
🔐 secretOAUTH_JWT_SECRET
🔐 secretOPENAI_API_KEY
🔐 secretQDRANT_API_KEY
configQDRANT_COLLECTIONqdrant.collection Vector collection name (env overrides)
configQDRANT_URL
configSLACK_BOT_MEMBER_TTL_MS
🔐 secretSLACK_BOT_TOKEN
🔐 secretSLACK_TOKEN
configSLACK_USERMAP_TTL_MS
🔐 secretSLACK_USER_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deploySUPABASE_SERVICE_ROLE_KEY
deploySUPABASE_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

14/14 tools missing one or more hints — list_drive_folder (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ping (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); railway_services (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

4 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 2 high severity in production deps — xlsx@0.18.5 (high), xlsx@0.18.5 (high)

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 6 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/chanthr-internal-mcp-1h1ta4?variant=verified)](https://m8ven.ai/mcp/chanthr-internal-mcp-1h1ta4)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0b4ecba5961a02096d50e99046a96604873c7155
code hash: a035fee08bd47ff9717d1db74b67f1bfda5d85669184d45280559ca0cb31db9d
verified: 8/19/2026, 8:29:51 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