THRONE
See report Verify server

registry / record

@notionhq/notion-mcp-server

npm / sealed 2026-06-12 / No. e91b23f9

> throne registry @notionhq/notion-mcp-server sealed
receiptsealed evidence
scan id
e91b23f9acd443cdad3e4fd660e22646
target
@notionhq/notion-mcp-server
sealed at
2026-06-12 06:50:42Z
evidence hash
sha256:17238ff4fc0546231c987d4429cd2f30f04a022b11278d7909bd0a08ffaaf99a
01connectPASS1.0s

initialize ok: server Notion API 1.0.0, negotiated protocolVersion 2025-11-25, capabilities ['tools']

02discoverPASS22ms

supported: tools/list (22 tools); method not found (tolerated): resources/list, prompts/list

03validate_schemasPASS466ms

all 22 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS1.4s

called 10 of 10 tools (cap 10): 10 ok, 0 returned tool-level errors (expected for synthesized args)

05error_handlingPASS4.2s

structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS0ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS2ms

resources capability not declared; not applicable (pass-na)

08concurrent_callsPASS449ms

ladder 1/2/4/8 overlapping API-get-users calls: max_observed_stable_concurrency=8; all ids answered exactly once at every level

09reconnectPASS930ms

transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)

01connectPASS904ms

initialize ok: server Notion API 1.0.0, negotiated protocolVersion 2025-11-25, capabilities ['tools']

02discoverPASS20ms

supported: tools/list (22 tools); method not found (tolerated): resources/list, prompts/list

03validate_schemasPASS406ms

all 22 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS1.2s

called 10 of 10 tools (cap 10): 10 ok, 0 returned tool-level errors (expected for synthesized args)

05error_handlingPASS4.3s

structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS0ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS2ms

resources capability not declared; not applicable (pass-na)

08concurrent_callsPASS625ms

ladder 1/2/4/8 overlapping API-get-users calls: max_observed_stable_concurrency=8; all ids answered exactly once at every level

09reconnectPASS945ms

transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)

chatgpt desktopemulation profile pending real-traffic captureCOMING SOON
SECURITY: REVIEW / 3 finding(s) / review material, not a verdict
LOWTHR-NET-05 / Hardcoded outbound endpoints

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:10
LOWTHR-VER-11 / Outdated MCP SDK or protocol version pin

obsolete protocol version string '2024-10-07' in source

package/bin/cli.mjs:152
LOWTHR-VER-11 / Outdated MCP SDK or protocol version pin

obsolete protocol version string '2024-11-05' in source

package/bin/cli.mjs:152
VERDICT: FIT TO SHIPSANDBOXED RUN — submitted server executed in a disposable microVM — compatibility: 0 fail / 0 warn across 2 clients / security: review — 3 finding(s), 0 highsealed by THRONE / No. e91b23f9 / 2026-06-12
THRONE: FIT TO SHIPwear the crown

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.

[![THRONE: FIT TO SHIP](https://api.usethrone.dev/api/badge/%40notionhq%2Fnotion-mcp-server)](https://usethrone.dev/server/notionhq-notion-mcp-server)
executed in a disposable microVM, created for this scan and destroyed after it. nothing outlives a run.

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.