Mmcp.market

Context Proxy MCP server

by kira-autonoma·io.github.kira-autonoma/context-proxy·v0.2.0·1 stars

MCP proxy that lazy-loads tool schemas to cut context token overhead by 6-7x

B72/100grade B
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
New

1 stars43 downloads/wk

Reviews

Write one

Nobody has reviewed Context Proxy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Context Proxy tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan17 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 193 days ago4/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Context Proxy in Claude Code, Cursor or VS Code

Runs npx -y mcp-lazy-proxy on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add context-proxy -- npx -y mcp-lazy-proxy
Add to Cursor

What the publisher says

From the Context Proxy repository's README, as published. We do not edit it. Read it on GitHub

mcp-lazy-proxy

Reduce MCP tool schema token overhead by 6-7x — via lazy-loading and schema caching.

Verified, not claimed. Every session writes a proof log to ~/.mcp-proxy-metrics.jsonl.

Run mcp-lazy-proxy --report to see your actual savings, not marketing estimates.

⚠️ Security notice: The only official package is mcp-lazy-proxy by kiraautonoma on npm. Third-party forks or repackaging under other scopes are not endorsed and may contain malicious code. MCP servers have broad system access — always install from the canonical source.

The Problem

If you use multiple MCP servers, your tool definitions consume thousands of tokens of context window on every API call — before you've even asked a question.

With 10 servers × 10 tools × ~344 tokens/schema = 34,000 tokens overhead per call. At $3/MTok (Claude Sonnet): $0.10 wasted per call, or $261/month at 100 calls/day.

The Solution

This proxy sits between your MCP client and upstream MCP servers. Instead of sending full tool schemas upfront, it:

  1. Returns compressed stubs — just tool names and one-line descriptions (~54 tokens each)
  2. Lazy-loads full schemas — only when a tool is actually invoked
  3. Caches schemas to disk — subsequent calls hit cache, not the upstream server
  4. Deduplicates — identical schemas across servers are stored once

Benchmark (real data)

\At $3/MTok input pricing, 100 API calls/day*

Quick Start

npm install -g mcp-lazy-proxy

Wrap a single MCP server

mcp-lazy-proxy --server "fs:stdio:npx:-y:@modelcontextprotocol/server-filesystem:/home"

Wrap multiple servers via config

{
  "servers": [
    {
      "id": "filesystem",
      "name": "Filesystem MCP",
      "transport": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/home"]
    },
    {
      "id": "github",
      "name": "GitHub MCP",
      "transport": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"]
    }
  ],
  "mode": "lazy"
}
mcp-lazy-proxy --config proxy.json

Use with Claude Desktop

{
  "mcpServers": {
    "proxy": {
      "command": "mcp-lazy-proxy",
      "args": ["--config", "/path/to/proxy.json"]
    }
  }
}

Modes

E2E Test Results

Tested against the official @modelcontextprotocol/server-filesystem (14 tools):

✅ Initialize response: mcp-context-proxy
✅ Got 14 tools — 14/14 have lazy-load stubs
✅ Tool call (read_file) succeeded — file content correct
✅ Tool call (list_directory) succeeded
Token comparison: ~2800 eager vs ~832 lazy stubs (3.4x on this small server)

With 10+ servers the ratio increases to 6-7x as schema complexity grows.

API (programmatic use)

import { MCPContextProxy } from 'mcp-lazy-proxy';

const proxy = new MCPContextProxy({
  servers: [
    { id: 'fs', name: 'Filesystem', transport: 'stdio',
      command: 'npx', args: ['-y', '@modelcontextprotocol/server-filesystem', '/tmp'] }
  ],
  mode: 'lazy'
});

await proxy.start();

Verifiable Savings Proof

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Context Proxy: common questions

Is Context Proxy MCP server safe?
Mostly: it is graded B (72/100). Read the Context Proxy safety report
How do I install Context Proxy?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Context Proxy need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Context Proxy maintained?
The last commit was 209 days ago (2026-03-18). The latest release is v0.2.0.
What can I use instead of Context Proxy?
Servers from other publishers that do the same job: Token Optimizer MCP server.

Alternatives to Context Proxy

Same job from other publishers: the closest match first, then the best rated.

  • Token Optimizer
    Context-window optimization: caching, compression & smart file tools that cut tokens 60-90%.
    C

More from kira-autonoma →