registry / record

@neondatabase/mcp-server-neon

npm / sealed 2026-06-16 / No. 1f9a20e0

Does @neondatabase/mcp-server-neon MCP work in Claude Code and Cursor? Throne executed @neondatabase/mcp-server-neon mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: not fit. Is @neondatabase/mcp-server-neon mcp safe? Static security scan: 1 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.

re-scan this server gate it in your CI

> throne registry @neondatabase/mcp-server-neon sealed

Upstream notice: the maintainer has deprecated this packageThis package is deprecated. Use the remote MCP server at mcp.neon.tech instead. See https://neon.tech/docs/ai/neon-mcp-server for more details.

receiptsealed evidence

scan id: 1f9a20e015664c5e9f4a4b245ec2cbe0
target: @neondatabase/mcp-server-neon
sealed at: 2026-06-16 18:11:14Z
evidence hash: sha256:c77c99f6294e95950101da3a9cf82b2bf0c1a0193b341ae857c81dbe7f3fa95f

01connectWARN30.1s

step timed out after 30s, threshold is assumed, not calibrated to real client behavior

02discoverFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

03validate_schemasFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

04smoke_test_toolsFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

05error_handlingFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

06streamingFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

07resource_lifecycleFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

08concurrent_callsFAIL0ms

RuntimeError: session not started, run step 1 (connect) first

09reconnectFAIL20.7s

RuntimeError: connect failed: McpError: Connection closed

01connectFAIL17.7s

RuntimeError: connect failed: McpError: Connection closed

02discoverSKIPPED0ms

not run, connect failed

03validate_schemasSKIPPED0ms

not run, connect failed

04smoke_test_toolsSKIPPED0ms

not run, connect failed

05error_handlingSKIPPED0ms

not run, connect failed

06streamingSKIPPED0ms

not run, connect failed

07resource_lifecycleSKIPPED0ms

not run, connect failed

08concurrent_callsSKIPPED0ms

not run, connect failed

09reconnectSKIPPED0ms

not run, connect failed

chatgpt desktop calibratingemulation profile pending real-traffic captureCOMING SOON

SECURITY: REVIEW / 1 finding(s) / review recommended

LOWTHR-NET-05 / Hardcoded outbound endpoints

5 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: b3564134667aa2dfeaa3992a12d9c12f (package/dist/constants.js:16), console.neon.tech (package/dist/constants.js:12), neon.tech (package/dist/initConfig.js:51), oauth2.neon.tech (package/dist/constants.js:10), track.neon.tech (package/dist/analytics/analytics.js:8)

package/dist/analytics/analytics.js:8

VERDICT: NOT FIT10 of 18 steps exercised across 2 clientsSANDBOXED RUN, submitted server executed in a disposable microVM, compatibility: 9 fail / 1 warn (10 of 18 steps exercised across 2 clients) / security: review, 1 finding(s), 0 highsealed by THRONE / No. 1f9a20e0 / 2026-06-16

scopeattestation tuple

target: @neondatabase/mcp-server-neon 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: 18 of 18
test suite: v1.0.0
security ruleset: v1.0.0
sealed at: 2026-06-16 18:11:14Z
evidence hash: sha256:c77c99f6294e95950101da3a9cf82b2bf0c1a0193b341ae857c81dbe7f3fa95f
valid until: 2026-09-14

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.