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. 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. 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.
How this item is evaluated
The microsoft/mcp-gateway record combines a 8.9/10 composite score with separate popularity (78.0), risk (medium), 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
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.