HALLUX
dev.blvkware/hallux
Check that a package, module or DOI exists before an agent installs, imports or cites it.
Description as published in the official MCP registry.
Answers the MCP handshake and lists its tools. Checked 2026-10-04.
What we measured
| Endpoint | https://api.blvkware.dev/hallux/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (1,849 ms) | our check, 2026-10-04 |
| Protocol version | 2025-11-25 | our check, 2026-10-04 |
| Tools (4) | hallux_check_command, hallux_check, hallux_check_manifest, hallux_watch | tools/list, 2026-10-04 |
| Registry version | 0.1.0 · active · updated 2026-09-23 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
claude mcp add --transport http hallux https://api.blvkware.dev/hallux/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name dev.blvkware/hallux.