Categories › Software Development › Code search, analysis, refactoring & languages
Check that a package, module or DOI exists before an agent installs, imports or cites it.
Remote server: your requests and data go to api.blvkware.dev. Claude Code: claude mcp add --transport http hallux https://api.blvkware.dev/hallux/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
hallux_check_command — Call this BEFORE running any command that installs or runs a dependency: npm/yarn/pnpm/bun install, npx, pip/uv/poetry/pipx, cargo add, go ghallux_check — Does this identifier actually exist, and is it safe? Call before acting on any name you recalled rather than read: a package to install, a mhallux_check_manifest — Call after writing or editing a dependency file and before committing or installing. Checks every dependency in one pass, including dev and hallux_watch — Register identifiers for a signed webhook when their verdict changes: phantom -> squat (someone registered a name models invent) or absent -hallux_report — Report identifiers a model produced that turned out not to exist. HALLUX verifies each against its registry and records only absent ones as hallux_account — Show remaining credits for the API key in use (or free-tier status), pricing, and where to buy credits with PayPal.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.