Feature
Keys stay on the server
Every Registry and Provider call runs in the app’s own server routes, so Provider keys and the GitHub token never reach the browser.
The browser calls only /api/check, /api/suggest and /api/providers. Those routes call the Registries and Providers, which also avoids cross-origin problems.
Keys are read from the server’s environment (.env.local when running locally).
More features
All features →- 01
Five Registries in one Check
npm, Homebrew Formulae, Homebrew Cask, PyPI and GitHub are asked in parallel; you get one Registry result per Registry.
- 02
Four Registry statuses
Every Registry result is Available, Taken, Error or Rate limited, so “unknown” is never shown as “free”.
- 03
Suggestions from a Provider
When a Name is Taken, pick a Provider and get 8 Suggestions: Claude API, OpenAI API, or Claude, Codex or Copilot through an MCP bridge.