mcpproxy-go — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Proxy MCP servers with tool discovery, OAuth and configurable management

What we know

Supercharge AI Agents, Safely Proxy MCP servers with tool discovery, OAuth and configurable management.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-09T20:35:38Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: modify proxy configuration; add upstream MCP servers; remove upstream MCP servers. Complete write authority is not verified.
Local install and proxy configuration; protect API key
Sensitive access: Upstream tool definitions, proxy logs and credentials

HTTP listener should stay on loopback by default; management operations, add/remove server and upstream credentials can be powerful.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

387 repository stars

Stars observed Oct 9, 2026.

Repository total for smart-mcp-proxy/mcpproxy-go.

All limitations / Review context

Has mcpproxy-go changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

HTTP listener should stay on loopback by default; management operations, add/remove server and upstream credentials can be powerful.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Local install and proxy configuration; protect API key
Upstream tool definitions, proxy logs and credentials
Reviewed write actions: modify proxy configuration; add upstream MCP servers; remove upstream MCP servers
Sensitive access: Upstream tool definitions, proxy logs and credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-09T20:35:38Z

Technical identity

github.com/smart-mcp-proxy/mcpproxy-go

Exact implementation source: https://github.com/smart-mcp-proxy/mcpproxy-go ↗
Reviewed resource type: Gateway
Repository identity: smart-mcp-proxy/mcpproxy-go

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
smart-mcp-proxy/mcpproxy-go
Recorded repository material and project history.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
MCPProxy runs an MCP gateway, managing downstream MCP servers for clients.
publisher documented install or connect · Publisher instructions
brew install smart-mcp-proxy/mcpproxy/mcpproxy
Configure / authenticate
MCP100 setup guide
Choose platform-specific MCPProxy Go installer or Homebrew formula, then follow publisher docs/setup.md for client registration; mcpproxy is gateway managing downstream servers, not an individual downstream server.
Check connection
Suggested check
Start gateway, inspect configured downstream server status and tool list through client, without invoking a write tool.
Remove / uninstall / revoke
Suggested check
Remove mcpproxy's registered endpoint from the MCP client, stop its service/tray daemon, then uninstall using the original package manager. Homebrew formula `brew uninstall mcpproxy`, cask `brew uninstall --cask mcpproxy` if those are its installed formula/cask names. Never delete proxy config/data by default.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.

Official Documentation & Sources

What it does

Supercharge AI Agents, Safely Proxy MCP servers with tool discovery, OAuth and configurable management.

Capability: Cloud & DevOps
Resource type: Gateway
Best fit: Proxy MCP servers with tool discovery, OAuth and configurable management

Representative uses

Connect multiple upstream MCP tools
Control access and server management
Configure local or remote client integrations
Proxy MCP servers with tool discovery, OAuth and configurable management

Limitations

HTTP listener should stay on loopback by default; management operations, add/remove server and upstream credentials can be powerful.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local install and proxy configuration; protect API key
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Upstream tool definitions, proxy logs and credentials
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: HTTP listener should stay on loopback by default; management operations, add/remove server and upstream credentials can be powerful.

Access scope and cautions

Write actions: Not verified modify proxy configuration add upstream MCP servers remove upstream MCP servers
Sensitive access: Upstream tool definitions, proxy logs and credentials
Risk level: high
Security notes: HTTP listener should stay on loopback by default; management operations, add/remove server and upstream credentials can be powerful.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which implementation does this page cover?

Supercharge AI Agents, Safely Proxy MCP servers with tool discovery, OAuth and configurable management.

What setup and authentication are documented?

Recorded installation/entrypoint step: go install github.com/smart-mcp-proxy/mcpproxy-go/cmd/mcpproxy@latest. Prerequisites: Compatible development runtime. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Default localhost proxy listener; network exposure requires API key, trusted host and TLS review. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local install and proxy configuration; protect API key

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: modify proxy configuration; add upstream MCP servers; remove upstream MCP servers. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Upstream tool definitions, proxy logs and credentials Recorded sensitive-access context: Upstream tool definitions, proxy logs and credentials.

What limitations and risks should I check before use?

HTTP listener should stay on loopback by default; management operations, add/remove server and upstream credentials can be powerful. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.

Why we’re tracking it

Best fit

What we know

Maintenance / activity evidence

Verification gaps / watch-outs

Popularity

Original activity observations

Evidence & Sources

Self-hosted gateway service setup

Install / connect

Configure / authenticate

Check connection

Remove / uninstall / revoke

Official Documentation & Sources

What it does

Representative uses

Limitations

Access & risk

Access scope and cautions

FAQ