io.github.giraygokirmak/tapebasis
Tapebasis
Is the Tapebasis MCP server down? It gave no valid answer in the probe of 2026-11-15: crashed on start. One failed probe is not an outage.
Market data from multiple independent providers, compared with clear provenance.
crashed on start no valid answer since 2026-11-15 · probed 2026-11-15
MCP error -32000: Connection closed error: failed to create directory `/work/uv`: Read-only file system (os error 30)
- Run it
- npx -y tapebasis@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/giraygokirmak/tapebasis
- Website
- https://github.com/giraygokirmak/tapebasis
- Registry
- active, updated 2026-11-15 · 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.giancarloerra/socraticode · alive
- io.github.gigatypeaura/memecorp-mcp · alive
- io.github.gilesdawe/tokei-agent · crashed on start
- io.github.giovanemartins/localstack · no executable
- io.github.girik-chadha/interviewer-mcp · alive
- io.github.girmmy/google-tasks · needs env
- MySQL MCP io.github.gistrec/mcp-mysql-client · alive
- Yandex Direct io.github.gistrec/mcp-yandex-direct · alive
Servers that mention independent or provenance.
- Aard ai.aard/aard · needs auth
- GroundTruth - Environmental Records ai.agentlookups/groundtruth · alive
- B4 Index ai.benroberts/b4-index · alive
- Decision Log ai.decisionlog/mcp · alive
- Duskly ai.duskly/duskly · alive
- GroundTruth — subsurface scan QA & trade estimating ai.gtfi/groundtruth · alive
- ai.jawz/jawz · alive
- Manpage MCP ai.manpage/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
- The package did not start as an MCP server at its probe on 2026-11-15. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.