registry / record
@notionhq/notion-mcp-server
Does @notionhq/notion-mcp-server MCP work in Claude Code and Cursor? Throne executed @notionhq/notion-mcp-server mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is @notionhq/notion-mcp-server mcp safe? Static security scan: 3 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry @notionhq/notion-mcp-server
sealed
- scan id
- da4b24e8340f4116b5f950de18664676
- target
- @notionhq/notion-mcp-server
- sealed at
- 2026-06-16 18:10:35Z
- evidence hash
- sha256:e7537693be01429475be12c5916f922f977500976189cd73c761b96b6e655abd
initialize ok: server Notion API 1.0.0, negotiated protocolVersion 2025-11-25, capabilities ['tools']
supported: tools/list (22 tools); method not found (tolerated): resources/list, prompts/list
all 22 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=serial): 10 ok, 0 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: API-get-user:accepted (returned result); API-get-users:accepted (returned result); API-get-self:accepted (returned result); API-post-search:accepted (returned result); API-get-block-children:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: error(-32603); recovery: accepted (returned result); cancellation: error(-32603); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1 overlapping API-get-users calls: max_observed_stable_concurrency=1; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server Notion API 1.0.0, negotiated protocolVersion 2025-11-25, capabilities ['tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (22 tools); method not found (tolerated): resources/list, prompts/list; notes: connection 2 confirms 22 tools
all 22 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=pipelined): 10 ok, 0 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: API-get-user:accepted (returned result); API-get-users:accepted (returned result); API-get-self:accepted (returned result); API-post-search:accepted (returned result); API-get-block-children:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: error(-32603); recovery: accepted (returned result); cancellation: error(-32603); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1/2/4/6 overlapping API-get-users calls: max_observed_stable_concurrency=6; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
5 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: api.notion.com (package/bin/cli.mjs:191), dub.sh (package/bin/cli.mjs:55), feross.org (package/bin/cli.mjs:396), git.io (package/bin/cli.mjs:10), www.notion.so (package/bin/cli.mjs:191)
package/bin/cli.mjs:10obsolete protocol version string '2024-10-07' in source
package/bin/cli.mjs:152obsolete protocol version string '2024-11-05' in source
package/bin/cli.mjs:152- target
- @notionhq/notion-mcp-server npm
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 14 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 18:10:35Z
- evidence hash
- sha256:e7537693be01429475be12c5916f922f977500976189cd73c761b96b6e655abd
- valid until
- 2026-09-14
paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/notionhq-notion-mcp-server)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.