Easy Notion MCP Server

easy-notion-mcp npm v1.1.0 Source verified

Published by grey-iris — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Token-efficient, markdown-first Notion MCP server where agents write markdown instead of raw Notion JSON.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/cli/init.js)MTC-SRC-002

In the server's implementation (`dist/cli/init.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from "node:child_process"; import { createInterface } from "node:readline/promises"; import { stdin as proc

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/init.js

medium Hardcoded egress to an external endpoint (dist/auth/oauth-provider.js)MTC-SRC-003

In the server's implementation (`dist/auth/oauth-provider.js:97`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: t tokenResponse = await fetch("https://api.notion.com/v1/oauth/token", { method: "POST",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/auth/oauth-provider.js

Tools 47

Each tool and what it can reach — statically extracted from the published source.

  • get_databasereads sensitive data
  • property-paginationreads sensitive data
  • query_databasereads sensitive data
  • add_commentno sensitive capability
  • add_database_entriesno sensitive capability
  • add_database_entryno sensitive capability
  • append_contentno sensitive capability
  • archive_pageno sensitive capability
  • archive_toggleno sensitive capability
  • create_databaseno sensitive capability
Show 37 more tools ↓
  • create_pageno sensitive capability
  • create_page_from_fileno sensitive capability
  • create_viewno sensitive capability
  • delete_database_entryno sensitive capability
  • delete_viewno sensitive capability
  • duplicate_pageno sensitive capability
  • find_replaceno sensitive capability
  • get_configno sensitive capability
  • get_meno sensitive capability
  • get_viewno sensitive capability
  • list_commentsno sensitive capability
  • list_databasesno sensitive capability
  • list_pagesno sensitive capability
  • list_usersno sensitive capability
  • list_viewsno sensitive capability
  • markdown-conventionsno sensitive capability
  • move_pageno sensitive capability
  • query_viewno sensitive capability
  • read_blockno sensitive capability
  • read_pageno sensitive capability
  • read_sectionno sensitive capability
  • read_toggleno sensitive capability
  • replace_contentno sensitive capability
  • restore_pageno sensitive capability
  • restore_toggleno sensitive capability
  • searchno sensitive capability
  • search_in_pageno sensitive capability
  • share_pageno sensitive capability
  • update_blockno sensitive capability
  • update_data_sourceno sensitive capability
  • update_database_entryno sensitive capability
  • update_pageno sensitive capability
  • update_sectionno sensitive capability
  • update_toggleno sensitive capability
  • update_viewno sensitive capability
  • update-data-source-guideno sensitive capability
  • warning-shapesno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 94/100 2 1.13.0 2026-08-28
v1.0.1 A 94/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/easy-notion-mcp/badge.svg)](https://mcptrustchecker.com/registry/easy-notion-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/easy-notion-mcp"><img src="https://mcptrustchecker.com/registry/easy-notion-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/easy-notion-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan easy-notion-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow