registry / record
not-a-valid-url
> throne registry not-a-valid-url
sealed
- scan id
- 6852bf4f754e4a8da7f6f5efa5e2f8bb
- target
- not-a-valid-url
- sealed at
- 2026-06-15 10:51:05Z
- evidence hash
- sha256:834a903769bcf2bc50d1c835adc3c7fe210636ed4b103325c71bf1735141f7ca
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-15T10_51_02_089Z-debug-0.log
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
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-15T10_51_02_089Z-debug-0.log
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
not run — server never launched
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.