Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
MCP adoption creates a second-order integration problem: too many separate servers, auth schemes, and transport details to manage cleanly. This matters because it treats MCP composition itself as the product, which is useful for teams that need one stable integration point instead of a pile of bespoke client wiring.
Who should use it
Who should skip it
Move on from metatool-ai/metamcp if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
metatool-ai/metamcp is tracked by RepoRadar as a code repository in the MCP infrastructure section. First seen 2026-07-19; the source record was last checked on 2026-07-19. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, metatool-ai/metamcp is strongest on workflow potential (9.1) and maturity (8.5) and weakest on setup ease (6.8) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar captured from https://github.com/metatool-ai/metamcp.
How this item is evaluated
The metatool-ai/metamcp record combines a 7.6/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
A gateway centralizes tool access, so a mistake in auth or routing can affect several downstream servers at once; Operators need to review what request and response data the proxy logs before routing sensitive tool traffic through it.