io.github.CloudCorpRecords/indexsearch
indexsearch
Is the io.github.CloudCorpRecords/indexsearch MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.
Elasticsearch tools: indices, mappings, query DSL search, ES|QL, and shards.
alive probed 2026-11-14 · unchanged since 2026-10-31
- Run it
- npx -y @reneturcios/indexsearch@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- indexsearch 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 497 tokens in Claude Opus 5.5, exact, measured 2026-10-31. With the Claude Code prefix mcp__…__ on each tool name: 547. The o200k_base estimate is 254. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/CloudCorpRecords/indexsearch
- Registry
- active, updated 2026-10-31 · 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.96×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| search | 133 | 68 | 27 % |
| get_shards | 115 | 59 | 23 % |
| get_mappings | 102 | 52 | 20 % |
| esql | 92 | 47 | 19 % |
| list_indices | 55 | 28 | 11 % |
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/importfix · alive
- io.github.CloudCorpRecords/importproof · alive
- io.github.CloudCorpRecords/inboxwatch · crashed on start
- io.github.CloudCorpRecords/indeeddata · alive
- io.github.CloudCorpRecords/infraport · alive
- io.github.CloudCorpRecords/injectcheck · alive
- io.github.CloudCorpRecords/instadata · alive
- io.github.CloudCorpRecords/installaudit · alive
Servers that mention elasticsearch or mappings.
- ai.getvda/elasticsearch-mongodb-redis-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/elasticsearch-redis-mysql-stack-generator · newer protocol
- ai.getvda/elasticsearch-redis-stack-generator · newer protocol
- ai.getvda/elasticsearch-redis-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/rabbitmq-elasticsearch-mongodb-stack-generator · newer protocol
- ai.getvda/rabbitmq-elasticsearch-mysql-stack-generator · newer protocol
- ai.getvda/rabbitmq-elasticsearch-postgres-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/rabbitmq-elasticsearch-postgres-stack-generator-mongo · newer protocol
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.