io.github.egoughnour/massive-context-mcp
io.github.egoughnour/massive-context-mcp
Is the io.github.egoughnour/massive-context-mcp MCP server down? No. It is up and needs network, probed 2026-10-26.
Handles 10M+ token contexts with chunking, sub-queries, and local Ollama inference.
needs network probed 2026-11-15 · unchanged since 2026-10-26
MCP error -32000: Connection closed OSError: [Errno 30] Read-only file system: 'mcpcost-placeholder' FileNotFoundError: [Errno 2] No such file or directory: 'mc
- Run it
- uvx massive-context-mcp@3.0.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/egoughnour/massive-context-mcp
- Registry
- active, updated 2026-01-19 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.egorthinks/perception · needs mcp<2
- io.github.egoughnour/code-firewall-mcp · needs env
- io.github.egoughnour/cowork-history · alive
- Curate-Ipsum io.github.egoughnour/curate-ipsum · needs env
- io.github.einvoice-dev1/archsteer · crashed on start
- io.github.elephia/elephia · needs env
- macOS Apps io.github.elfensky/macos-apps-mcp · install failed
- Memory Fabric io.github.elViRafa/memory-fabric · needs args
Servers that mention massive.
- Polygon Io io.github.pipeworx-io/polygon-io · alive
- OpenGrok MCP Server io.github.IcyHot09/opengrok · error
- OpenGrok MCP Server io.github.IcyHot09/opengrok-mcp-server · needs env
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-26 07:01 | needs network | ||||
| 2026-10-19 06:51 | needs env |
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 tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.