HALLUX
REMOTE · API.BLVKWARE.DEV · SCANNED SEP 25
Check that a package, module or DOI exists before an agent installs, imports or cites it.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 728 tokens (~121/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the HALLUX MCP server?
HALLUX is a hosted endpoint at https://api.blvkware.dev/hallux/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.blvkware.dev
claude mcp add --transport http dev-blvkware-hallux 'https://api.blvkware.dev/hallux/mcp'
{
"mcpServers": {
"dev-blvkware-hallux": {
"url": "https://api.blvkware.dev/hallux/mcp"
}
}
} {
"servers": {
"dev-blvkware-hallux": {
"type": "http",
"url": "https://api.blvkware.dev/hallux/mcp"
}
}
} [mcp_servers.dev-blvkware-hallux] url = "https://api.blvkware.dev/hallux/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-blvkware-hallux": {
"type": "remote",
"url": "https://api.blvkware.dev/hallux/mcp",
"enabled": true
}
}
} openclaw mcp add dev-blvkware-hallux --url 'https://api.blvkware.dev/hallux/mcp' --transport streamable-http
mcp_servers:
dev-blvkware-hallux:
url: "https://api.blvkware.dev/hallux/mcp" {
"McpServers": {
"dev-blvkware-hallux": {
"Transport": "http",
"Url": "https://api.blvkware.dev/hallux/mcp"
}
}
} assistant mcp add dev-blvkware-hallux -t streamable-http -u 'https://api.blvkware.dev/hallux/mcp'
{
"mcpServers": {
"dev-blvkware-hallux": {
"type": "http",
"url": "https://api.blvkware.dev/hallux/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +4
- Tool coverage: 83% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- Tool “hallux_check” now declares an output schema ▲ functional
- Tool “hallux_check_command” now declares an output schema ▲ functional
- Tool “hallux_check_manifest” now declares an output schema ▲ functional
- Tool “hallux_watch” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- MCP protocol version: 2024-11-05 → 2025-11-25 functional
- “hallux_watch” reworded the description of “identifiers” cosmetic
- 23 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://api.blvkware.dev/hallux/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.blvkware.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 663326231baa207eb9c49dba51cc4a9d8c7 |
| SANs: api.blvkware.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.blvkware.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| blvkware.dev. | present | 57190 | 13 | Verified |
| api.blvkware.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.blvkware.dev/hallux/mcp | Verified | 200 | |
| http (plaintext) | http://api.blvkware.dev/hallux/mcp | HTTPS enforced | 301 | https://api.blvkware.dev/hallux/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hallux_check Check identifiers ~197
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 the registry. Do not proceed phantom - does not exist AND models repeatedly invent it. Do not proceed squat - was invented by models, then registered by someone. Treat as hostile unknown - could not verify. Never treat this as permission Live namespaces: cite.doi, pkg.crates, pkg.go, pkg.maven, pkg.npm, pkg.nuget, pkg.pypi. An unsupported namespace returns `unknown`, never an error, so it is safe to ask.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiers | array | yes | Up to 100 identifiers. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | array | – | The absent, phantom and squat results. |
| checked | integer | – | How many identifiers were checked. |
| decision | string | yes | BLOCK: do not proceed. REVIEW: something could not be verified. PROCEED: every identifier exists. NOTHING_TO_CHECK: no identifier was recognised. |
| results | array | yes | Every result, in input order. |
| safeToProceed | boolean | yes | False whenever anything was blocked. |
| unverified | array | – | The unknown results. |
No examples provided.
hallux_check_command Check an install command before running it ~173
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 one runs attacker code. You cannot tell the difference by looking at the name, which is why this check exists. Pass the command exactly as you intend to run it. The identifiers are extracted for you. If the result says BLOCK, do not run the command. Use the `successor` if one is given, otherwise tell the user what was found and stop.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The shell command, verbatim. Example: pip install requests requests-oauth2-helper |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | array | – | The absent, phantom and squat results. |
| checked | integer | – | How many identifiers were checked. |
| command | string | – | The command as received. |
| decision | string | yes | BLOCK: do not proceed. REVIEW: something could not be verified. PROCEED: every identifier exists. NOTHING_TO_CHECK: no identifier was recognised. |
| identifiersFound | array | – | The identifiers read off the command. |
| results | array | yes | Every result, in input order. |
| safeToProceed | boolean | yes | False whenever anything was blocked. |
| unverified | array | – | The unknown results. |
No examples provided.
hallux_check_manifest Check a dependency file ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The file contents. |
| filename | string | yes | The file name, e.g. package.json. Path is ignored; only the name is used to pick a parser. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | array | – | The absent, phantom and squat results. |
| checked | integer | – | How many identifiers were checked. |
| decision | string | yes | BLOCK: do not proceed. REVIEW: something could not be verified. PROCEED: every identifier exists. NOTHING_TO_CHECK: no identifier was recognised. |
| filename | string | – | The file name as received. |
| results | array | yes | Every result, in input order. |
| safeToProceed | boolean | yes | False whenever anything was blocked. |
| unverified | array | – | The unknown results. |
No examples provided.
hallux_watch Be told if a name turns hostile later ~119
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 worth monitoring. Delivered by signed webhook to a URL you supply.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string | yes | An https URL to POST transitions to. |
| identifiers | array | yes | Up to 100 identifiers to watch, typically ones that came back absent or phantom. |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | – |
| event | string | – | – |
| registered | array | yes | – |
| signature | object | – | – |
| transitionOfInterest | string | – | – |
No examples provided.
What is the HALLUX MCP server?
HALLUX is an MCP server listed in the public MCP registry as dev.blvkware/hallux. Check that a package, module or DOI exists before an agent installs, imports or cites it. This page covers its hosted endpoint (https://api.blvkware.dev/hallux/mcp).
Is the HALLUX MCP server safe to use?
HALLUX scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HALLUX MCP server expose?
HALLUX exposes 4 tools: hallux_check_command, hallux_check, hallux_check_manifest, hallux_watch. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Does the HALLUX MCP server require authentication?
No. We connected to HALLUX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HALLUX MCP server still maintained?
HALLUX is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.