Back to MCP Trust Indexm8ven
D
Caution
54/100
16 days ago

notion-mcp

An MCP server for the Notion API, enabling management of pages, databases, files, comments, and users with native markdown support and a full file pipeline.

→ snickery/notion-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

snickery

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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

// 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 4 credentials: NOTION_TOKEN, GOOGLE_CLIENT_SECRET, MCP_BEARER_TOKEN, XBERG_VLM_API_KEY
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.
configNOTION_BATCH_CONCURRENCY
configPDF_MAX_CONCURRENCY
🔐 secretNOTION_TOKENexport =ntn_...
configNOTION_API_VERSIONNo 2026-03-11 Notion API version header
configGOOGLE_TOKEN_DB_PATHFor Drive /google-data/tokens.db Path to google-accounts-mcp's SQLite token DB (read-only; the legacy GMAIL_TOKEN_DB_PATH name is still honored)
configGMAIL_TOKEN_DB_PATHGOOGLE_TOKEN_DB_PATH For Drive /google-data/tokens.db Path to google-accounts-mcp's SQLite token DB (read-only; the legacy name is still honored)
configDRIVE_ACCOUNTFor Drive Google account email for Drive access
configDRIVE_FOLDER_NAMEFor Drive mcp-google-accounts Shared Drive folder name
configGOOGLE_CLIENT_IDFor Drive OAuth client ID (same as google-accounts-mcp)
🔐 secretGOOGLE_CLIENT_SECRETFor Drive OAuth client secret
configFILES_DIRlocation string no "files" "files" (the notion-mcp private store, ) or "shared" (the cross-MCP mount, SHARED_DIR, populated by google-accounts-mcp download_attachment(destination='shared'))
configSHARED_DIRlocation string no "files" "files" (the notion-mcp private store, FILES_DIR) or "shared" (the cross-MCP mount, , populated by google-accounts-mcp download_attachment(destination='shared'))
🔐 secretMCP_BEARER_TOKENYes Bearer token for authenticating MCP clients
configXBERG_BASE_URL
configXBERG_TIMEOUT
configXBERG_VLM_MODEL
configXBERG_VLM_BASE_URL
🔐 secretXBERG_VLM_API_KEY
configXBERG_OCR_BACKEND
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

44/44 tools missing one or more hints — notion_search_pages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); notion_search_databases (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); notion_list_files_on_page (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +41 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.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — notion_purge_shared_files deletes at line 457 (p.unlink()); notion_purge_file deletes at line 478 (target.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

43/44 tool handlers declare input schemas (98%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 3/44 tool handlers wrap calls in try/catch (7%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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/snickery-notion-mcp-1gj01w?variant=verified)](https://m8ven.ai/mcp/snickery-notion-mcp-1gj01w)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c2735681f14ca31d410b93822926dac519de2745
code hash: 90fdfe861d6efc03b378c1277018182fe95f67c7c4ce9ce4f13c216ccb3759d6
verified: 8/6/2026, 9:05:31 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