MCP.Market

My Cool Proxy MCP server

by karashiiro·io.github.karashiiro/my-cool-proxy·v1.5.4·15 stars

An MCP server gateway that minimizes context usage via progressive Lua-driven discovery 🌙

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

full report

Adoption
Growing

15 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed My Cool Proxy yet.

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

My Cool 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-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan319 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 152 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How My Cool Proxy compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
GitHub stars
15
more than 90% of 28,688 servers
Downloads a week
35
more than 25% of 12,191 servers with a package

Install My Cool Proxy in Claude Code, Cursor or VS Code

Runs npx -y @karashiiro/my-cool-proxy on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add my-cool-proxy -- npx -y @karashiiro/my-cool-proxy
Add to Cursor

What the publisher says

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

My Cool Proxy

My Cool Proxy is a Model Context Protocol (MCP) server gateway that tries to solve a lot of perceived problems with MCP as it exists today. In no particular order, those are that:

  • Tool descriptions bloat the context window: This is a problem with how most agents integrate with MCP. Rather than implementing abstractions that enable tools to be loaded as needed, most applications dump all MCP tools into the context at once. To mitigate this, My Cool Proxy wraps tools in a Lua interpreter and exposes higher-level tools for discovering tools incrementally. Refer to Progressive Disclosure for more information.
  • Tool results bloat the context window, why not use Bash? Rather than using MCP tools, agents could just execute terminal commands and use bash to filter their results - however, this means allowing the agent to perform high-risk actions more frequently. For example, you could allow an agent to use the gh CLI to interact with GitHub, but it can then use the gh CLI to perform mutating or destructive operations, as well. With the GitHub MCP Server, you can instead scope things down to read-only tools trivially. MCP allows you to tightly control what tools agents have access to. To assist with this, My Cool Proxy allows you to further filter the tools exposed to agents.
  • Most MCP features are unsupported: Unfortunately, most applications only expose MCP tools to agents, neglecting the other client and server features offered by the protocol. My Cool Proxy aims to be a common abstraction layer for as many protocol features as possible, which allows developers to use the full capabilities of MCP in any MCP-compatible application. This is a work in progress - check the feature support table for more details.
  • Managing a config file for multiple agents is a pain: If you use more than a single MCP-compatible application, you'll quickly run into challenges keeping your MCP server configuration synchronized across them. My Cool Proxy solves this by acting as a single integration point for every server you use, reducing the number of servers to keep in sync down to just one.

Quick Start

0. Installation

Install it globally to use it as a CLI tool:

npm install -g @karashiiro/my-cool-proxy

Or run it directly via npx:

npx @karashiiro/my-cool-proxy

1. Configure

The gateway auto-creates a default config on first run. Just run it once to generate the config file:

my-cool-proxy  # Creates config and starts (with no servers)

# Find your config location
my-cool-proxy --config-path

Then edit the config to add your MCP servers.

Example config structure:

{
  "port": 3000,
  "host": "localhost",
  "mcpClients": {
    "my-server": {
      "type": "http",
      "url": "https://example.com/mcp"
    }
  }
}

Or, copy the example config for a more complete starting point.

2. Run

# If installed globally
my-cool-proxy

# If running via npx
npx @karashiiro/my-cool-proxy

3. Connect

Add it to your MCP client config in e.g. Claude Desktop:

{
  "mcpServers": {
    "my-cool-proxy": {
      "url": "http://localhost:3000/mcp"
    }
  }
}

4. Use It

Ask your agent to perform a task that your configured MCP servers can help with, and watch it run!

Progressive Disclosure

Shortened. The full README is on GitHub.

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

My Cool Proxy: common questions

Is My Cool Proxy MCP server safe?
Mostly: it is graded B (82/100). Read the My Cool Proxy safety report
How do I install My Cool Proxy?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does My Cool Proxy need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is My Cool Proxy maintained?
The last commit was 188 days ago (2026-04-30). The latest release is v1.5.4.
How does My Cool Proxy compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); github stars 15 (more than 90% of 28,688 servers); downloads a week 35 (more than 25% of 12,191 servers with a package). Full comparison.