Looking for public Chrome DevTools MCP startup failure logs to test safe failure-window extraction

[rileyross722]

Hi everyone, I’m looking for a few public Chrome DevTools MCP startup, CI, install, or terminal failure logs to test whether a “safe failure-window” workflow is useful for coding agents.

I saw issue #199, where adding chrome-devtools-mcp in an MCP client produced an ERR_MODULE_NOT_FOUND error around:

chrome-devtools-mcp/build/src/browser.js

That issue is already closed, so I’m not trying to reopen it or add noise there. I’m using it only as an example of the kind of failure pattern I’m interested in:

• MCP server startup failure
• ERR_MODULE_NOT_FOUND
• package/runtime path issue
• coding-agent or IDE MCP client context
• stack trace where the useful failure signal is buried inside a larger log

What I’m testing

I’m testing FailLens Crash Gate, which does one narrow thing:

failed command log -> redacted bounded failure evidence -> agent-safe next step

No install is needed for the first test.

If someone has a public failed Chrome DevTools MCP startup log, GitHub Actions failure, install failure, or terminal crash related to MCP setup, feel free to reply with a public link or paste a redacted excerpt.

What I can return

I can run it through FailLens and reply with a safe summary like:

failure type:
failure subject:
bounded evidence window:
safe_to_send:
likely next action:

I will not publish raw logs, secrets, private repo names, or stack trace bodies in any public proof without permission.

Good example

A good example is:

MCP server failed to start
log is noisy
useful error is buried
an agent or developer needs the small part that matters

If this kind of validation post is not appropriate for this discussion area, I’m happy to remove it. I’m mainly looking for real MCP/devtool failure examples to see whether this workflow is useful outside my own test cases.