Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want one MCP surface for comparing model options and launching media-generation tasks from inside their coding tool, but who should verify the hosted-service and pricing-snapshot trade-offs before leaning on it heavily.
Who should use it
Who should skip it
Skip runapi-ai/mcp for now if you are only tracking items with a 'try now' verdict.
About this signal
runapi-ai/mcp is tracked by RepoRadar as a model catalog mcp in the MCP section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'worth watch' with a Silver tier and easy setup difficulty. runapi-ai/mcp leads on setup ease (8.8) and workflow potential (8.5); its lowest signal is maturity (5.6), so factor that in before investing setup time. 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 runapi-ai/mcp a composite score of 7.7 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
Task creation and balance checks require a real RUNAPI_API_KEY and send work to the hosted RunAPI service; Catalog and pricing data are shipped as build-time snapshots, so freshness depends on the package being released again.