Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for MCP-heavy agent setups that need a policy checkpoint instead of blindly attaching more servers: start with a small internal tool set, verify the quarantine and approval flow, then decide whether it really reduces token and safety overhead.
Who should use it
Who should skip it
Skip smart-mcp-proxy/mcpproxy-go if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
smart-mcp-proxy/mcpproxy-go is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. Across RepoRadar's eight signals, smart-mcp-proxy/mcpproxy-go is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (4.2) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The smart-mcp-proxy/mcpproxy-go record combines a 8.6/10 composite score with separate popularity (52.0), risk (conditional), and setup (advanced) 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
It brokers access to external MCP tools and approval policy, so a lax configuration can still expose risky tool servers or sensitive credentials to agent sessions.