Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for platform teams that are moving from one-off MCP experiments to shared infrastructure: it gives them a cleaner way to route tool traffic, keep sessions sticky, and manage multiple servers without inventing the control plane from scratch.
Who should use it
Who should skip it
Hold off on microsoft/mcp-gateway for mission-critical workflows without a containment strategy, explicit approvals, and a hands-on security review.
About this signal
microsoft/mcp-gateway is tracked by RepoRadar as a framework 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. The standout signals for microsoft/mcp-gateway are workflow potential (10.0) and practical usefulness (9.0), while setup ease (4.2) trails — that balance shapes where it fits best. 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 microsoft/mcp-gateway a composite score of 8.9 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 78.0 and never affects the composite score or tier. The risk label of 'medium' 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
This gateway sits in the middle of agent tool traffic and can concentrate access to multiple MCP servers, so review its auth model and deployment boundary before routing sensitive tools through it.