registry / record

not-a-valid-url

npm / sealed 2026-06-20 / No. 2d72cfc0

Does not-a-valid-url MCP work in Claude Code and Cursor? Throne executed not-a-valid-url mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: inconclusive. Is not-a-valid-url mcp safe? Static security scan: not run (the server did not launch far enough to scan). 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 not-a-valid-url sealed

This target couldn't be started as an MCP serverserver process exited with code 1 before the MCP handshake, stderr: npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/not-a-valid-url - Not found npm error 404 npm error 404 'not-a-valid-url@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T09_01_52_985Z-debug-0.log

receiptsealed evidence

scan id: 2d72cfc0b48e4410ae7dd9ff69cfe0e5
target: not-a-valid-url
sealed at: 2026-06-20 09:01:54Z
evidence hash: sha256:76de7284b9bce5de6d9f453b8b2637c6f227b174e290af5beb484e025695caed

01connectFAIL0ms

server never launched: server process exited with code 1 before the MCP handshake, stderr: npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/not-a-valid-url - Not found npm error 404 npm error 404 'not-a-valid-url@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T09_01_52_985Z-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 code E404 npm error 404 Not Found - GET https://registry.npmjs.org/not-a-valid-url - Not found npm error 404 npm error 404 'not-a-valid-url@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T09_01_52_985Z-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

SECURITY: NOT RUN

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 code E404 npm error 404 Not Found - GET https://registry.npmjs.org/not-a-valid-url - Not found npm error 404 npm error 404 'not-a-valid-url@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/worker/.npm/_logs/2026-06-20T09_01_52_985Z-debug-0.log / security scan skippedsealed by THRONE / No. 2d72cfc0 / 2026-06-20

scopeattestation tuple

target: not-a-valid-url 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 09:01:54Z
evidence hash: sha256:76de7284b9bce5de6d9f453b8b2637c6f227b174e290af5beb484e025695caed
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.