Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
The MCP ecosystem is expanding faster than its deployment ergonomics. mcp-proxy matters because it gives developers a simple control point for exposing and managing multiple MCP servers, while making the token-handling and proxy-layer trust decisions explicit.
Who should use it
Who should skip it
Skip tbxark/mcp-proxy unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
tbxark/mcp-proxy is tracked by RepoRadar as a code repository in the MCP infrastructure section. First seen 2026-07-18; the source record was last checked on 2026-07-18. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, tbxark/mcp-proxy is strongest on workflow potential (8.7) and open-source/build quality (8.4) and weakest on setup ease (6.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar captured from https://github.com/tbxark/mcp-proxy.
How this item is evaluated
The tbxark/mcp-proxy record combines a 7.2/10 composite score with separate popularity (100.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The proxy can hold and refresh downstream OAuth tokens, so operators need to trust its credential storage and access boundaries; Any proxy that centralizes multiple tool backends becomes a higher-leverage control point if misconfigured or exposed too broadly.