THRONE
See report Verify server

registry / record

a

npm / sealed 2026-06-20 / No. 4464942e

Does a MCP work in Claude Code and Cursor? Throne executed a mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: inconclusive. Is a mcp safe? Static security scan: no findings under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.

> throne registry a sealed
This target couldn't be started as an MCP serverserver process exited with code 1 before the MCP handshake, stderr: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T06_59_03_911Z-debug-0.log
receiptsealed evidence
scan id
4464942e1f2447348e5d1f9ffc292e43
target
a
sealed at
2026-06-20 06:59:05Z
evidence hash
sha256:04d2fa8c730588824427397e2e5653fd3a4e56e54f9be14852087d3717eb10ab
01connectFAIL0ms

server never launched: server process exited with code 1 before the MCP handshake, stderr: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T06_59_03_911Z-debug-0.log

02discoverSKIPPED0ms

not run, server never launched

03validate_schemasSKIPPED0ms

not run, server never launched

04smoke_test_toolsSKIPPED0ms

not run, server never launched

05error_handlingSKIPPED0ms

not run, server never launched

06streamingSKIPPED0ms

not run, server never launched

07resource_lifecycleSKIPPED0ms

not run, server never launched

08concurrent_callsSKIPPED0ms

not run, server never launched

09reconnectSKIPPED0ms

not run, server never launched

01connectFAIL0ms

server never launched: server process exited with code 1 before the MCP handshake, stderr: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T06_59_03_911Z-debug-0.log

02discoverSKIPPED0ms

not run, server never launched

03validate_schemasSKIPPED0ms

not run, server never launched

04smoke_test_toolsSKIPPED0ms

not run, server never launched

05error_handlingSKIPPED0ms

not run, server never launched

06streamingSKIPPED0ms

not run, server never launched

07resource_lifecycleSKIPPED0ms

not run, server never launched

08concurrent_callsSKIPPED0ms

not run, server never launched

09reconnectSKIPPED0ms

not run, server never launched

chatgpt desktop calibratingemulation profile pending real-traffic captureCOMING SOON
No findings under security ruleset v1
VERDICT: INCONCLUSIVESANDBOXED RUN, submitted server executed in a disposable microVM, compatibility not assessable: server never launched: server process exited with code 1 before the MCP handshake, stderr: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T06_59_03_911Z-debug-0.log / security: clean, 0 findingssealed by THRONE / No. 4464942e / 2026-06-20
scopeattestation tuple
target
a 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-20 06:59:05Z
evidence hash
sha256:04d2fa8c730588824427397e2e5653fd3a4e56e54f9be14852087d3717eb10ab
valid until
2026-09-18
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.