Skip to content

HALLUX MCP server

dev.blvkware/halluxblvkware.devstreamable-httpv1.1.0Scanned

Verify that packages, images, repos and DOIs an AI recalled exist before an agent uses them.

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 1
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HALLUX MCP server can do

The HALLUX MCP server is published by blvkware.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: hallux_check_command, hallux_check, hallux_check_manifest, hallux_watch and 1 more), but cannot delete data. 1 tool only reads.

6 tools bring in text other people can write (hallux_check_command, hallux_check, hallux_check_manifest and 3 more); 1 tool can send data out of your system (hallux_watch).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 5Claude Code: ask
  • hallux_checkDoes this identifier actually exist, and is it safe?Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Does this identifier actually exist, and is it safe? Call before acting on any name you recalled rather than read: a package to install, a module to import, a Docker image, a GitHub Action or repo, a DOI to cite. Verdicts: exists (proceed, but read `risk`), deprecated (use `successor`), absent (not in the registry; do not proceed), phantom (absent AND models repeatedly invent it), squat (a name models invent that someone has since registered; treat as hostile), unknown (could not verify; never treat as permission). For names that exist, `risk` flags typosquats, LLM-style name conflations, brand-new packages and names registered after agents looked them up.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Does this identifier exist?
  • hallux_check_commandCall this BEFORE running any command that installs or runs a dependency: npm/yarn/pnpm/bun install, npx, pip/uv/poetry/pipx, cargo add, go get, dotnet add package, gem install, com…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The input takes a statement or command to run (input.command), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "hallux_check_command" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this BEFORE running any command that installs or runs a dependency: npm/yarn/pnpm/bun install, npx, pip/uv/poetry/pipx, cargo add, go get, dotnet add package, gem install, composer require, dart pub add, docker pull/run, git clone. Language models invent plausible package names that have never existed, and attackers register those names because they can predict them (slopsquatting). Installing one runs attacker code. You cannot tell by looking at the name. Pass the command exactly as you intend to run it. Decision: ALLOW (run it), REVIEW (tell the user about the risk signals first), BLOCK (do not run; use `successor` if given, otherwise tell the user), UNVERIFIED (registry unreachable; do not treat as safe).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Check an install command
  • hallux_check_manifestCall after writing or editing a dependency file and before committing or installing.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "hallux_check_manifest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call after writing or editing a dependency file and before committing or installing. Checks every dependency in one pass, including dev and optional groups, where an invented name usually arrives. Exact pinned versions are verified too. Supported: package.json, requirements.txt, pyproject.toml, Pipfile, Cargo.toml, go.mod, Gemfile, composer.json, *.csproj / packages.config, pubspec.yaml, mix.exs, Dockerfile, .github/workflows/*.yml.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Check a dependency file
  • hallux_reportReport identifiers a model produced that turned out not to exist.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Report identifiers a model produced that turned out not to exist. HALLUX verifies each against its registry and records only absent ones as attestations in the public hallucination ledger, which is how names graduate to `phantom` and get watched for squatting. Requires an API key.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Report a hallucinated name
  • hallux_watchRegister identifiers for a signed webhook when their verdict changes: phantom -> squat (someone registered a name models invent) or absent -> exists.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.callbackUrl): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Register identifiers for a signed webhook when their verdict changes: phantom -> squat (someone registered a name models invent) or absent -> exists. Use for a name that came back absent/phantom which the user still intends to use, or a dependency set worth monitoring. Requires an API key; costs 25 credits ($0.02) per identifier per 30 days.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • title: Watch names for registration
Only reads 1Show 1 read-only tool
  • hallux_accountShow remaining credits for the API key in use (or free-tier status), pricing, and where to buy credits with PayPal.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Show remaining credits for the API key in use (or free-tier status), pricing, and where to buy credits with PayPal.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Credits and pricing

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:51 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.blvkware.dev/hallux/mcp: tools/list returned 6 tools to an anonymous client, including hallux_check_command (write), hallux_check (write), hallux_check_manifest (write), hallux_watch (write), hallux_report (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 4 to 5

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "hallux_check_command" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "hallux_check_manifest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff
  2. Tools2 added, 4 changed.+2 added~4 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
    • Tools that change things, listed without credentials: 4 to 5

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hallux__hallux_account"
    ],
    "ask": [
      "mcp__hallux__hallux_check_command",
      "mcp__hallux__hallux_check",
      "mcp__hallux__hallux_check_manifest",
      "mcp__hallux__hallux_watch",
      "mcp__hallux__hallux_report"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hallux. Review it before you use it.

Capability tags behind 6 rules
  • mcp__hallux__hallux_check_command untrusted-input
  • mcp__hallux__hallux_check untrusted-input
  • mcp__hallux__hallux_check_manifest untrusted-input
  • mcp__hallux__hallux_watch untrusted-input, outbound
  • mcp__hallux__hallux_report untrusted-input
  • mcp__hallux__hallux_account untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.blvkware/hallux/verify?hash=195ca3c75b746588f4d168c1cec1bfbb29d83baaea239fa3a446cbec7b08dd02" | jq -e '.changed == false'

Pinned hash 195ca3c75b74, from Nov 21, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.blvkware/hallux/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.blvkware/hallux
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.blvkware/hallux.svg)](https://radar.anlyon.com/servers/dev.blvkware/hallux)

Source: MCP Registry. Synced Nov 21, 2026, 10:17 UTC.

HALLUX MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HALLUX MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the HALLUX MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the HALLUX MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the HALLUX MCP server have?

6 tools: 5 write, 1 read. hallux_check_command, hallux_check, hallux_check_manifest, hallux_watch, hallux_report and hallux_account.

Does the HALLUX MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HALLUX MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): hallux_watch.

Has the HALLUX MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.