io.github.egoughnour/massive-context-mcp
PYPI · MASSIVE-CONTEXT-MCP · 2 COMPONENTS · SCANNED SEP 20
Handles 10M+ token contexts with chunking, sub-queries, and local Ollama inference.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 244 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1406 tokens (~82/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rlm_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.egoughnour/massive-context-mcp server?
io.github.egoughnour/massive-context-mcp runs locally as a PyPI package, launched with uvx massive-context-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · massive-context-mcp
claude mcp add egoughnour-massive-context-mcp -- uvx massive-context-mcp
{
"mcpServers": {
"egoughnour-massive-context-mcp": {
"command": "uvx",
"args": [
"massive-context-mcp"
]
}
}
} {
"servers": {
"egoughnour-massive-context-mcp": {
"command": "uvx",
"args": [
"massive-context-mcp"
]
}
}
} codex mcp add egoughnour-massive-context-mcp -- uvx massive-context-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"egoughnour-massive-context-mcp": {
"type": "local",
"command": [
"uvx",
"massive-context-mcp"
],
"enabled": true
}
}
} openclaw mcp add egoughnour-massive-context-mcp --command uvx --arg massive-context-mcp
mcp_servers:
egoughnour-massive-context-mcp:
command: "uvx"
args: ["massive-context-mcp"] {
"McpServers": {
"egoughnour-massive-context-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"massive-context-mcp"
]
}
}
} assistant mcp add egoughnour-massive-context-mcp -t stdio -c uvx -a massive-context-mcp
{
"mcpServers": {
"egoughnour-massive-context-mcp": {
"command": "uvx",
"args": [
"massive-context-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 −4
- Stability: pass → 0.77 functional
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Provenance & Transparency fell 1.
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/massive-context-mcp@3.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
rlm_auto_analyze Rlm Auto Analyze ~122
Automatically detect content type and analyze with optimal chunking strategy. One-step analysis for common tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | integer | – | Max parallel requests (default 4, max 8) |
| content | string | yes | The content to analyze |
| goal | string | yes | Analysis goal: 'summarize', 'find_bugs', 'extract_structure', 'security_audit', or 'answer:<your question>' |
| name | string | yes | Context identifier |
| provider | string | – | LLM provider - 'auto' prefers Ollama if available |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_chunk_context Rlm Chunk Context ~71
Chunk a loaded context by strategy. Returns chunk metadata, not full content.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Context identifier |
| size | integer | – | Chunk size (lines/chars depending on strategy) |
| strategy | string | – | Chunking strategy - 'lines', 'chars', or 'paragraphs' |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_exec Rlm Exec ~75
Execute Python code against a loaded context in a sandboxed subprocess. Set result variable for output.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Python code to execute. User sets result variable for output. |
| context_name | string | yes | Name of previously loaded context |
| timeout | integer | – | Max execution time in seconds (default 30) |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_filter_context Rlm Filter Context ~72
Filter context using regex/string operations. Creates a new filtered context.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | 'keep' or 'remove' matching lines |
| name | string | yes | Source context identifier |
| output_name | string | yes | Name for filtered context |
| pattern | string | yes | Regex pattern to match |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_firewall_status Rlm Firewall Status ~123
Check the status of the code execution firewall. Returns information about whether the firewall is enabled, the Ollama endpoint being used, and whether dangerous code patterns will be blocked. The firewall is auto-enabled when code-firewall-mcp is installed: pip install massive-context-mcp[firewall] Returns: { "enabled": bool, "package_installed": bool, "ollama_url": str, "embedding_model": str, "similarity_threshold": float, "ollama_reachable": bool, }
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
rlm_get_chunk Rlm Get Chunk ~48
Get a specific chunk by index. Use after chunking to retrieve individual pieces.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_index | integer | yes | Index of chunk to retrieve |
| name | string | yes | Context identifier |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
rlm_get_results Rlm Get Results ~26
Retrieve stored results for aggregation.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Result set identifier |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
rlm_inspect_context Rlm Inspect Context ~52
Inspect a loaded context - get structure info without loading full content into prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Context identifier |
| preview_chars | integer | – | Number of chars to preview (default 500) |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_list_contexts Rlm List Contexts ~19
List all loaded contexts and their metadata.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
rlm_load_context Rlm Load Context ~48
Load a large context as an external variable. Returns metadata without the content itself.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full context content |
| name | string | yes | Identifier for this context |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_ollama_status Rlm Ollama Status ~79
Check Ollama server status and available models. Returns whether Ollama is running, list of available models, and if the default model (gemma3:12b) is available. Use this to determine if free local inference is available.
| Name | Type | Req | Description |
|---|---|---|---|
| force_refresh | boolean | – | Force refresh the cached status (default: false) |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_setup_ollama Rlm Setup Ollama ~160
Install Ollama via Homebrew (macOS). Requires Homebrew pre-installed. Uses 'brew install' and 'brew services'. PROS: Auto-updates, pre-built binaries, managed service. CONS: Requires Homebrew, may prompt for sudo on first Homebrew install.
| Name | Type | Req | Description |
|---|---|---|---|
| install | boolean | – | Install Ollama via Homebrew (requires Homebrew) |
| model | string | – | Model to pull (default: gemma3:12b). Use gemma3:4b or gemma3:1b for lower RAM systems. |
| pull_model | boolean | – | Pull the default model (gemma3:12b) |
| start_service | boolean | – | Start Ollama as a background service via brew services |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_setup_ollama_direct Rlm Setup Ollama Direct ~166
Install Ollama via direct download (macOS). Downloads from ollama.com to ~/Applications. PROS: No Homebrew needed, no sudo required, fully headless, works on locked-down machines. CONS: Manual PATH setup, no auto-updates, service runs as foreground process.
| Name | Type | Req | Description |
|---|---|---|---|
| install | boolean | – | Download and install Ollama to ~/Applications (no sudo needed) |
| model | string | – | Model to pull (default: gemma3:12b). Use gemma3:4b or gemma3:1b for lower RAM systems. |
| pull_model | boolean | – | Pull the default model (gemma3:12b) |
| start_service | boolean | – | Start Ollama server (ollama serve) in background |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_store_result Rlm Store Result ~50
Store a sub-call result for later aggregation.
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | – | – | Optional metadata about this result |
| name | string | yes | Result set identifier |
| result | string | yes | Result content to store |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rlm_sub_query Rlm Sub Query ~116
Make a sub-LLM call on a chunk or filtered context. Core of recursive pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_index | – | – | Optional: specific chunk index |
| context_name | string | yes | Context identifier to query against |
| model | – | – | Model to use (provider-specific defaults apply) |
| provider | string | – | LLM provider - 'auto', 'ollama', or 'claude-sdk'. 'auto' prefers Ollama if available (free local inference) |
| query | string | yes | Question/instruction for the sub-call |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_sub_query_batch Rlm Sub Query Batch ~118
Process multiple chunks in parallel. Respects concurrency limit to manage system resources.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_indices | array | yes | List of chunk indices to process |
| concurrency | integer | – | Max parallel requests (default 4, max 8) |
| context_name | string | yes | Context identifier |
| model | – | – | Model to use (provider-specific defaults apply) |
| provider | string | – | LLM provider - 'auto', 'ollama', or 'claude-sdk' |
| query | string | yes | Question/instruction for each sub-call |
Structured output declared, but exposes no named fields.
No examples provided.
rlm_system_check Rlm System Check ~61
Check if system meets requirements for Ollama with gemma3:12b. Verifies: macOS, Apple Silicon (M1/M2/M3/M4), 16GB+ RAM, Homebrew installed. Use before attempting Ollama setup.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.egoughnour/massive-context-mcp server?
io.github.egoughnour/massive-context-mcp is listed in the public MCP registry as io.github.egoughnour/massive-context-mcp. Handles 10M+ token contexts with chunking, sub-queries, and local Ollama inference. This page covers its PyPI package (massive-context-mcp).
Is the io.github.egoughnour/massive-context-mcp server safe to use?
io.github.egoughnour/massive-context-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.egoughnour/massive-context-mcp server expose?
io.github.egoughnour/massive-context-mcp exposes 17 tools: rlm_system_check, rlm_setup_ollama, rlm_setup_ollama_direct, rlm_ollama_status, rlm_load_context, and 12 more. Their descriptions and schemas cost roughly 1,406 tokens of context every time the server is loaded.
Is the io.github.egoughnour/massive-context-mcp server still maintained?
io.github.egoughnour/massive-context-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.egoughnour/massive-context-mcp server under?
io.github.egoughnour/massive-context-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.