notion-mcp-server@0.1.1
VERIFIED· not startedPublisher claims: "Powerful MCP server for Notion - read, create, search, and manage pages and databases through Claude" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
NOTION_TOKENConfiguration, not credentials: DEFAULT_PARENT_PAGE_ID, DEFAULT_PRIVACY- Where it talks to
- notion.so (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for NOTION_TOKEN and talks to notion.so. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Check NOTION_TOKEN in your .env file."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose." • Set DEFAULT_PARENT_PAGE_ID in .env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose." 2. Set DEFAULT_PARENT_PAGE_ID in .env to your preferred parent\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Requires DEFAULT_PARENT_PAGE_ID in .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Either provide parent_id, set DEFAULT_PARENT_PAGE_ID in .env, "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."DEFAULT_PARENT_PAGE_ID not set in .env. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.If None, uses DEFAULT_PARENT_PAGE_ID from .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Get one at https://www.notion.so/my-integrations and add to .env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for notion-mcp-server@0.1.1 as of 27 h ago. This is the package itself, not its dependencies.