registry / record
@elastic/mcp-server-elasticsearch
> throne registry @elastic/mcp-server-elasticsearch
sealed
- scan id
- 81b5d05e87e640d29565da941b2e4711
- target
- @elastic/mcp-server-elasticsearch
- sealed at
- 2026-06-12 18:49:57Z
- evidence hash
- sha256:1e3abfeaf6dd416b7f94b897f975ad559d7bd638fec25bd5acfbf0e83ba2dab7
server never launched: server process exited with code 1 before the MCP handshake — stderr: "type": "string", "inclusive": true, "exact": false, "message": "Elasticsearch URL cannot be empty", "path": [ "url" ] }, { "validation": "url", "code": "invalid_string", "message": "Invalid Elasticsearch URL format", "path": [ "url" ] } ]
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: "type": "string", "inclusive": true, "exact": false, "message": "Elasticsearch URL cannot be empty", "path": [ "url" ] }, { "validation": "url", "code": "invalid_string", "message": "Invalid Elasticsearch URL format", "path": [ "url" ] } ]
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
"prepare" runs on git-dependency installs and local dev (not registry installs): 'npm run build'
package/package.json"prepare" runs on git-dependency installs and local dev (not registry installs): 'npm run build'
package/dist/package.jsonmaintainer 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.