io.github.awkoy/notion-mcp-server
NPM · NOTION-MCP-SERVER · SCANNED SEP 20
Token-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security97
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 83 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to awkoy/notion-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1061 tokens (~265/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability check failed: the tool surface changed between 2.13.0 and 3.1.0: 1 tool removals, 0 breaking changes, 2 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.awkoy/notion-mcp-server server?
io.github.awkoy/notion-mcp-server runs locally as an npm package, launched with npx -y notion-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · notion-mcp-server
claude mcp add awkoy-notion-mcp-server -- npx -y notion-mcp-server
{
"mcpServers": {
"awkoy-notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"notion-mcp-server"
]
}
}
} {
"servers": {
"awkoy-notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"notion-mcp-server"
]
}
}
} codex mcp add awkoy-notion-mcp-server -- npx -y notion-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"awkoy-notion-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"notion-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add awkoy-notion-mcp-server --command npx --arg -y --arg notion-mcp-server
mcp_servers:
awkoy-notion-mcp-server:
command: "npx"
args: ["-y", "notion-mcp-server"] {
"McpServers": {
"awkoy-notion-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"notion-mcp-server"
]
}
}
} assistant mcp add awkoy-notion-mcp-server -t stdio -c npx -a -y notion-mcp-server
{
"mcpServers": {
"awkoy-notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"notion-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 19 Sept 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 50 to 30.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
- 16 Sept 26 +15
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Package version: 3.0.1 → 3.1.0 functional
- 15 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 3.0.0 → 3.0.1 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 12 Sept 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 50 to 30.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/notion-mcp-server@3.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | awkoy/notion-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/awkoy/notion-mcp-server/.github/workflows/publish-npm.yml@refs/tags/v3.1.0 |
| Rekor log index | 2867493842 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fd22b72cbf55109167bcea2c3a5433c58e1ac02b4f3338226f33e342c6bfbd9300c9798ea0a889855602ff1d05d2cb2aa0545690abad750811226e3ca |
Background: How many MCP packages publish verified provenance →
Dependencies 83 packages
| Packages resolved | 83 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
notion_describe Notion Describe ~93
Return the JSON Schema and a working example for one operation, plus which tool runs it (notion_read or notion_write). Use this BEFORE calling the operation when the payload shape is non-trivial (query filters, structured block trees, database property definitions). For simple ops, just call it — errors carry the schema.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | Operation name to describe, as listed by notion_read / notion_write. |
No output schema declared.
No examples provided.
notion_read Notion Read ~267
Run one Notion read operation by name. Nothing is modified. Call: { operation, payload } — payload carries that operation's fields. Common: search_pages { query }, get_page { page_id }, get_page_markdown { page_id }, query_database { database_id, where? }, get_block_children { block_id }. Responses are slimmed; pass verbose:true in payload for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link. A block link's #fragment is used for block_id fields and a database link's ?v= for view_id fields. If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (query_database filters).
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | The read operation to run. This list is the complete menu of read operations enabled on this server; notion_describe(operation) returns any operation's full schema. |
| payload | object | yes | Operation parameters. Pass either single-op fields directly, or { items: [...], atomic?, idempotency_key?, concurrency? } for batch. |
No output schema declared.
No examples provided.
notion_write Notion Write ~307
Run one Notion write operation by name. Archive, trash and delete operations remove content — confirm with the user before running them. Two ways to call: • Single: { operation: "set_page_title", payload: { page_id, title } } • Batch: { operation: "set_page_title", payload: { items: [{page_id, title}, ...], atomic?: false, idempotency_key?: "...", concurrency?: 3 } } create_page, append_blocks, update_block and update_page_markdown also take a markdown string. Responses are slimmed; pass verbose:true inside payload (single) or per item (batch) for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link. If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (block trees, database property definitions, batch_mixed_blocks).
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | The write operation to run. This list is the complete menu of write operations enabled on this server; notion_describe(operation) returns any operation's full schema. |
| payload | object | yes | Operation parameters. Pass either single-op fields directly, or { items: [...], atomic?, idempotency_key?, concurrency? } for batch. |
No output schema declared.
No examples provided.
What is the io.github.awkoy/notion-mcp-server server?
io.github.awkoy/notion-mcp-server is listed in the public MCP registry as io.github.awkoy/notion-mcp-server. Token-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents. This page covers its npm package (notion-mcp-server).
Is the io.github.awkoy/notion-mcp-server server safe to use?
io.github.awkoy/notion-mcp-server scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.awkoy/notion-mcp-server server expose?
io.github.awkoy/notion-mcp-server exposes 3 tools: notion_read, notion_write, notion_describe. Their descriptions and schemas cost roughly 667 tokens of context every time the server is loaded.
Is the io.github.awkoy/notion-mcp-server server still maintained?
io.github.awkoy/notion-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.awkoy/notion-mcp-server server under?
io.github.awkoy/notion-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.