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. It was first seen on 2026-06-19 and last updated 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. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned smart-mcp-proxy/mcpproxy-go a composite score of 8.6 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 52.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
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.