Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want one serious API client that works for both human debugging and agent-driven request orchestration without handing secrets to a cloud dashboard.
Who should use it
Who should skip it
Skip voleeo/voleeo-api unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
voleeo/voleeo-api is tracked by RepoRadar as a developer tool in the API / MCP section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, voleeo/voleeo-api is strongest on workflow potential (9.7) and open-source/build quality (8.4) and weakest on momentum (6.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 voleeo/voleeo-api a composite score of 8.2 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 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
It can expose live API requests, tokens, and environments to an MCP client, so first evaluation should stay on scrubbed or non-production workspaces; The project is explicitly labeled early access, so expect rough edges before you replace a stable production API client with it.