HALLUX

Name: HALLUX
Author: dev.blvkware

MCP serverMCP

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

by dev.blvkwarehomepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"hallux","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability63/63 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	169 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
10 h ago	mcp initialize	ok	200	173 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
17 h ago	mcp initialize	ok	200	180 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
24 h ago	mcp initialize	ok	200	166 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
30 h ago	mcp initialize	ok	200	174 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	177 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	173 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	177 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	174 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	166 ms	server hallux 0.1.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

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. Languag
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. Ret
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.
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 regis

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

content.writingWriting & Editing100%dev.package-managementPackages & Dependencies100%communication.notificationsNotifications58%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrydev.blvkware/hallux

first seen 17 d ago · fetched 11 h agoopen ↗

Field history (6 recent events)

17 d ago · declared · summary → "Check that a package, module or DOI exists before an agent installs, imports or cites it."
17 d ago · declared · description → "Check that a package, module or DOI exists before an agent installs, imports or cites it."
17 d ago · declared · publisherName → "dev.blvkware"
17 d ago · declared · homepageUrl → "https://blvkware.dev/hallux/"
17 d ago · declared · version → "0.1.0"
17 d ago · declared · protocols → ["mcp"]