io.github.CloudCorpRecords/prbody
prbody
Is the io.github.CloudCorpRecords/prbody MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-03.
Build a PR body from its commits, the linked issue, and the repo's PR template.
alive probed 2026-11-14 · unchanged since 2026-11-03
- Run it
- npx -y @reneturcios/prbody@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- prbody 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 314 tokens in Claude Opus 5.5, exact, measured 2026-11-03. With the Claude Code prefix mcp__…__ on each tool name: 322. The o200k_base estimate is 183. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/prbody
- 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.72×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| build_pr_body | 314 | 183 | 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/planboard · alive
- io.github.CloudCorpRecords/policyrecall · alive
- io.github.CloudCorpRecords/porefind · alive
- io.github.CloudCorpRecords/poworacle · alive
- io.github.CloudCorpRecords/prepboard · alive
- io.github.CloudCorpRecords/previewglow · alive
- io.github.CloudCorpRecords/privatesearch · alive
- io.github.CloudCorpRecords/procureport · alive
Servers that mention template or commits.
- Pro Reach LinkedIn Outreach ai.proreach/outreach · needs auth
- Shipstar ai.shipstar/mcp · needs auth
- thirds.ai ai.thirds/thirds · needs auth
- Panel Review ai.truverif/panel-review · needs auth
- ai.smithery/anirbanbasu-pymcp · not found
- ai.smithery/devbrother2024-typescript-mcp-server-boilerplate · not found
- Kanbai — public project templates and SOPs app.kanbai/discovery · alive
- LetX app.letx/letx · needs auth
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.