All servers · Research & knowledge

HALLUX

dev.blvkware/hallux · v0.1.0

Measured by MCP Station

Description written by the publisher, not verified

Check that a package, module or DOI exists before an agent installs, imports or cites it.

Connect

claude mcp add --transport http hallux https://api.blvkware.dev/hallux/mcp

{
  "mcpServers": {
    "hallux": {
      "url": "https://api.blvkware.dev/hallux/mcp"
    }
  }
}

Tools as reported by the server

• hallux_check_command
  Call this BEFORE running any command that installs a dependency: npm, yarn, pnpm, bun, pip, uv, poetry, pipx, cargo, go get, dotnet add package, nuget. Language models invent plausible package names that have never existed, and attackers register those names because they can predict them. Installing
• hallux_check
  Does this identifier actually exist? Call before acting on any name you recalled rather than read: a package to install, a module to import, a DOI to cite. Returns one of: exists, deprecated, absent, phantom, squat, unknown. exists - proceed deprecated - proceed, but use `successor` absent - not in
• hallux_check_manifest
  Call this after writing or editing a dependency file, and before committing it. Supported: package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod. Checks every dependency in one pass, including dev and optional groups, which is where an invented name usually arrives.
• hallux_watch
  Register identifiers for notification when their verdict changes. The transition that matters is phantom to squat: a name models invent that somebody then registers. Use this for a dependency that came back `absent` or `phantom` and that the user intends to use anyway, or for a set of dependencies w

Website · JSON · Text for agents · Registry updated 2026-09-23