io.github.crewhaus/validation
io.github.crewhaus/validation
Is the io.github.crewhaus/validation MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
AI startup idea validation by a specialized 9-agent crew.
not found down since 2026-10-16 · probed 2026-11-14 · unchanged since 2026-10-30
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y crewhaus-mcp-server@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/crewhaus/crewhaus-mcp-server
- Registry
- active, updated 2026-03-02 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.crawlbrulee/mcp · alive
- Crawlerpeek io.github.crawlerpeek/crawlerpeek · alive
- io.github.creatorscore/creatorscore-mcp · alive
- io.github.creis-ai/mcp-property-valuation-server · alive
- io.github.crissyfield/super-trouper · crashed on start
- LiteScope io.github.croc100/litescope · crashed on start
- 2D Assets MCP io.github.crony-io/2d-assets-mcp · alive
- io.github.cryptoeights/hyre-mcp · alive
Servers that mention validation.
- MainBook Bank Statement Converter ai.mainbook/bank-statement-converter · alive
- ai.plith/plith · alive
- SignalHarness.ai ai.signalharness/mcp · server error
- ai.smithery/DynamicEndpoints-powershell-exec-mcp-server · not found
- Branddock app.branddock/branddock · needs auth
- Locio Australian addresses au.com.locio/addresses · needs auth
- com.abundanceapis/abundance-apis · alive
- com.acuris-geo/acuris-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-16, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.