registry / record
@neondatabase/mcp-server-neon
> throne registry @neondatabase/mcp-server-neon
sealed
- scan id
- 12449caa29ae4abc893f398975132ef6
- target
- @neondatabase/mcp-server-neon
- sealed at
- 2026-06-12 15:22:16Z
- evidence hash
- sha256:169fae31462bec20a2e7357c55f065722c57b190a927e73b4b7134fe7a1261ec
step timed out after 10s
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
step timed out after 10s
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
not run — connect failed
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:8maintainer 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.