io.github.CloudCorpRecords/libdocs-remote
libdocs-remote
Is the io.github.CloudCorpRecords/libdocs-remote MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.
Forward Context7 library documentation lookups to the hosted remote MCP endpoint.
alive probed 2026-11-01
- Run it
- npx -y @reneturcios/libdocs-remote@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- libdocs-remote 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 392 tokens in Claude Opus 5.5, exact, measured 2026-11-01. With the Claude Code prefix mcp__…__ on each tool name: 416. The o200k_base estimate is 213. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/libdocs-remote
- Registry
- active, updated 2026-11-01 · 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.84×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| get-library-docs | 271 | 147 | 69 % |
| resolve-library-id | 121 | 66 | 31 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- io.github.CloudCorpRecords/libdocs npmjs.com
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.