io.github.openpoem/spec-score-mcp
io.github.openpoem/spec-score-mcp
Is the io.github.openpoem/spec-score-mcp MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
Score your specs before feeding them to an LLM. MCP server with radar chart visualization.
not found down since 2026-10-20 · probed 2026-11-15 · unchanged since 2026-10-27
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 spec-score-mcp@2.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/openpoem/spec-score-mcp
- Registry
- active, updated 2026-02-28 · 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.openflowkit/openflowkit-mcp · crashed on start
- io.github.openfused/openfuse-mcp · crashed on start
- io.github.opengameapp/browser-game · alive
- io.github.opengolfapi/mcp-server · alive
- io.github.openpouch/openpouch · alive
- OpenPulsechain Analytics io.github.openpulsechain/analytics · alive
- OpenReadout io.github.openreadout/openreadout · alive
- Scout io.github.openscout-app/scout · crashed on start
Servers that mention score.
- GroundTruth - Environmental Records ai.agentlookups/groundtruth · alive
- Arclan MCP Registry ai.arclan/registry · alive
- BittleBits GEO Assistant ai.bittlebits/bittlebits · no DNS
- B4 Index ai.benroberts/b4-index · alive
- CertScore.ai MCP Light ai.certscore/mcp-light · alive
- Builders in Fintech ai.buildersinfintech/fintech-data · alive
- ai.colaunched/colaunched · needs auth
- ai.colaunched/public · 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-20, 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.