Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that already have documented APIs and want to expose them to MCP-capable agents quickly without writing a custom server per backend.
Who should use it
Who should skip it
Consider therealm-tech/oas2mcp lower priority if you already have a working solution in this category.
About this signal
therealm-tech/oas2mcp is tracked by RepoRadar as a mcp tooling in the Developer Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, therealm-tech/oas2mcp is strongest on workflow potential (9.3) and open-source/build quality (8.4) and weakest on momentum (5.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. 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 therealm-tech/oas2mcp a composite score of 7.8 out of 10, placing it in the Silver 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 1.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
Auth passthrough and header forwarding can expose real upstream tokens or privileged APIs to agent calls, so start with a low-privilege spec and review the transport boundary carefully; One generated tool per API operation can widen the callable surface quickly, so use the JWT role gate or a reduced spec before exposing sensitive backends.