io.github.CloudCorpRecords/backportcheck
backportcheck
Is the io.github.CloudCorpRecords/backportcheck MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-03.
Decide whether a fix needs a backport, and to which release branches.
alive probed 2026-11-14 · unchanged since 2026-11-03
- Run it
- npx -y @reneturcios/backportcheck@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- backportcheck 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 338 tokens in Claude Opus 5.5, exact, measured 2026-11-03. With the Claude Code prefix mcp__…__ on each tool name: 348. The o200k_base estimate is 195. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/backportcheck
- Registry
- active, updated 2026-11-02 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.73×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| check_backport | 338 | 195 | 100 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.CloudCorpRecords/asinlens · alive
- io.github.CloudCorpRecords/askboard · alive
- io.github.CloudCorpRecords/assetlens · alive
- io.github.CloudCorpRecords/audioport · alive
- io.github.CloudCorpRecords/backtestport · alive
- io.github.CloudCorpRecords/ballpark · alive
- io.github.CloudCorpRecords/banditkeep · alive
- io.github.CloudCorpRecords/bilitrack · alive
Servers that mention backport or branches.
- Layerz io.github.layerzlabs/layerz · needs auth
- PlanetScale io.github.planetscale/mcp-server · needs auth
- Xata io.github.xataio/mcp · needs auth
- In Bmv io.github.pipeworx-io/in-bmv · alive
- TalentLMS MCP by usefulapi io.usefulapi/talentlms · timeout
- Scribase com.scribase/scribase · alive
- Baron io.github.zanaat-dev/baron · crashed on start
- LibraryAPI dev.libraryapi/libraryapi-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 server answers initialize and tools/list. Nothing to fix.