registry / record
@modelcontextprotocol/server-puppeteer
> throne registry @modelcontextprotocol/server-puppeteer
sealed
- scan id
- 3bd52f69cba74b2e829d84c97b8dc31f
- target
- @modelcontextprotocol/server-puppeteer
- sealed at
- 2026-06-12 06:55:34Z
- evidence hash
- sha256:4937e5b7cabb9e59941241ba8867469db6dc32f2e2f0a2a2913ebc21f7539870
initialize ok: server example-servers/puppeteer 0.1.0, negotiated protocolVersion 2024-11-05, capabilities ['resources', 'tools']
supported: tools/list (7 tools), resources/list (1); method not found (tolerated): prompts/list
all 7 tool inputSchemas are valid JSON Schema
called 7 of 7 tools (cap 10): 0 ok, 7 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived — wrong_type_args: error(-32603); unknown_method: error(-32601); invalid_id: no response (silent), connection alive
no streaming-capable tool declared by this server; not applicable (pass-na)
read console://logs (1 content blocks); subscribe capability not declared (pass-na)
ladder 1/2/4/8 overlapping puppeteer_navigate calls: max_observed_stable_concurrency=8; all ids answered exactly once, but every call returned an error (error -32603: Failed to launch the browser process! undefined [1007:1029:0612/065502.812818:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1007:1007:0612/065502.814423:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY [1007:1007:0612/065502.814436:ERROR:env.cc(257)] The platform failed to initialize. Exiting. TROUBLESHOOTING: https://pptr.dev/troubleshooting ) — the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2024-11-05, first session was 2024-11-05)
initialize ok: server example-servers/puppeteer 0.1.0, negotiated protocolVersion 2024-11-05, capabilities ['resources', 'tools']
supported: tools/list (7 tools), resources/list (1); method not found (tolerated): prompts/list
all 7 tool inputSchemas are valid JSON Schema
called 7 of 7 tools (cap 10): 0 ok, 7 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived — wrong_type_args: error(-32603); unknown_method: error(-32601); invalid_id: no response (silent), connection alive
no streaming-capable tool declared by this server; not applicable (pass-na)
read console://logs (1 content blocks); subscribe capability not declared (pass-na)
ladder 1/2/4/8 overlapping puppeteer_navigate calls: max_observed_stable_concurrency=8; all ids answered exactly once, but every call returned an error (error -32603: Failed to launch the browser process! undefined [1737:1759:0612/065521.108316:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [1737:1737:0612/065521.109563:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY [1737:1737:0612/065521.109576:ERROR:env.cc(257)] The platform failed to initialize. Exiting. TROUBLESHOOTING: https://pptr.dev/troubleshooting ) — the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2024-11-05, first session was 2024-11-05)
"prepare" runs on git-dependency installs and local dev (not registry installs): 'npm run build'
package/package.jsonpaste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/modelcontextprotocol-server-puppeteer)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.