io.github.RCOLKITT/vaspera-pm
io.github.RCOLKITT/vaspera-pm
Is the io.github.RCOLKITT/vaspera-pm MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Verify docs against code, detect drift, and generate verified specs (MCP server).
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
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 vaspera-pm@2.15.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/RCOLKITT/VasperaPM
- Website
- https://vasperapm.com
- Registry
- active, updated 2026-07-19 · 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.R1ghtHereWaiting/engagelab-email · needs env
- Reins io.github.R2Rlabs/hyperliquid-reins · needs env
- Reins io.github.R2Rlabs/reins · needs env
- io.github.RCOLKITT/vaspera-hardening · not found
- io.github.RCOLKITT/vasperamemory · crashed on start
- io.github.RCS-kz/bitrix24-mcp · crashed on start
- io.github.RCS-kz/mcp-1c · crashed on start
- io.github.RECERQA/rq-scan · alive
Servers that mention generate or verified.
- Getlead ad.getle/leads · alive
- 1325.AI ai.1325/mcp · needs auth
- AFG: agents hire agents (test money) ai.afg/afg · alive
- Agentic Terminal Directory ai.agenticterminal/directory · alive
- ai.atlasverified/atlas-mcp · needs auth
- AI Media Studio ai.b77/ai-media-studio · needs auth
- Autoposting ai.autoposting/autoposting · not MCP
- BotInfo — Advanced Robot Market Data ai.botinfo/robot-market-data · 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-17, 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.