# HALLUX (remote · api.blvkware.dev)

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

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.blvkware.dev`: 77/100 (this document), [markdown](https://verifymcp.io/servers/dev-blvkware-hallux/hallux-mcp.md), [page](https://verifymcp.io/servers/dev-blvkware-hallux/hallux-mcp)

## Channel facts

- Endpoint: `https://api.blvkware.dev/hallux/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "dev-blvkware-hallux": {
      "type": "http",
      "url": "https://api.blvkware.dev/hallux/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-blvkware-hallux]
url = "https://api.blvkware.dev/hallux/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-blvkware-hallux": {
      "type": "remote",
      "url": "https://api.blvkware.dev/hallux/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-blvkware-hallux --url 'https://api.blvkware.dev/hallux/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-blvkware-hallux:
    url: "https://api.blvkware.dev/hallux/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-blvkware-hallux": {
      "Transport": "http",
      "Url": "https://api.blvkware.dev/hallux/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-blvkware-hallux -t streamable-http -u 'https://api.blvkware.dev/hallux/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 77, +4)

- [functional improvement] Tool coverage: 83% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] MCP protocol: fail → pass
- [functional improvement] Tool “hallux_check” now declares an output schema
- [functional improvement] Tool “hallux_check_command” now declares an output schema
- [functional improvement] Tool “hallux_check_manifest” now declares an output schema
- [functional improvement] 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
- [cosmetic] “hallux_watch” reworded the description of “identifiers”

### 2026-09-23 (score 73)

First indexed and scored.

## MCP tools (4)

### `hallux_check_command` (~173 tokens)

Check an install command before running it

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.

Input parameters:

- `command` (string, required): The shell command, verbatim. Example: pip install requests requests-oauth2-helper

Output parameters:

- `blocked` (array): The absent, phantom and squat results.
- `checked` (integer): How many identifiers were checked.
- `command` (string): The command as received.
- `decision` (string): 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): Every result, in input order.
- `safeToProceed` (boolean): False whenever anything was blocked.
- `unverified` (array): The unknown results.

### `hallux_check` (~197 tokens)

Check identifiers

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.

Input parameters:

- `identifiers` (array, required): Up to 100 identifiers.

Output parameters:

- `blocked` (array): The absent, phantom and squat results.
- `checked` (integer): How many identifiers were checked.
- `decision` (string): BLOCK: do not proceed. REVIEW: something could not be verified. PROCEED: every identifier exists. NOTHING_TO_CHECK: no identifier was recognised.
- `results` (array): Every result, in input order.
- `safeToProceed` (boolean): False whenever anything was blocked.
- `unverified` (array): The unknown results.

### `hallux_check_manifest` (~107 tokens)

Check a dependency file

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.

Input parameters:

- `content` (string, required): The file contents.
- `filename` (string, required): The file name, e.g. package.json. Path is ignored; only the name is used to pick a parser.

Output parameters:

- `blocked` (array): The absent, phantom and squat results.
- `checked` (integer): How many identifiers were checked.
- `decision` (string): 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): Every result, in input order.
- `safeToProceed` (boolean): False whenever anything was blocked.
- `unverified` (array): The unknown results.

### `hallux_watch` (~119 tokens)

Be told if a name turns hostile later

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.

Input parameters:

- `callbackUrl` (string, required): An https URL to POST transitions to.
- `identifiers` (array, required): Up to 100 identifiers to watch, typically ones that came back absent or phantom.

Output parameters:

- `decision` (string)
- `event` (string)
- `registered` (array)
- `signature` (object)
- `transitionOfInterest` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-blvkware-hallux/hallux-mcp#diagnostics

## Score history

- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://api.blvkware.dev/hallux/mcp
- Website: https://blvkware.dev/hallux/
- Changelog RSS feed: https://verifymcp.io/servers/dev-blvkware-hallux/hallux-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-blvkware-hallux/hallux-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-blvkware-hallux/hallux-mcp