Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who are already juggling multiple model providers and want one local endpoint plus transparent token and latency tracking instead of scattering keys, formats, and cost visibility across several clients.
Who should use it
Who should skip it
Skip mxyhi/token_proxy if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
mxyhi/token_proxy is tracked by RepoRadar as a local ai api gateway in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for mxyhi/token_proxy are workflow potential (9.6) and practical usefulness (9.0), while momentum (6.0) trails — that balance shapes where it fits best. 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 mxyhi/token_proxy a composite score of 8.1 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The proxy sits in front of real provider keys and can transform request and response formats, so start with low-privilege keys and audit the config before routing sensitive traffic; The desktop workflow stores local configuration and token history on the host, so treat the machine as part of your credential and usage boundary.