Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hawl

NPM · HAWL.AI

Mailbox, handoffs and permits between your coding agents. Local mode needs no account.

Available components

npm · hawl.ai 56
+4 this week 56 Trust /100

Last scanned (2 hours ago)

Scores higher than 35% of npm servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 46 tokens (~46/item across 0 items; 0 tools + 0 resources), lean.Pass
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 0
    • Package version: 0.1.8 → 0.1.14 functional
    • Package version: 0.1.8 → 0.1.12 functional
    • Package version: 0.1.8 → 0.1.11 functional
  • 20 Oct 26 +21
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → fail ▼ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.17 ▲ functional
    • Package version: 0.1.7 → 0.1.8 functional
  • 19 Oct 26 −18
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.3 → 0.1.7 functional
  • 15 Oct 26 52

    First indexed and scored.

Diagnostics

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 24 Oct 2026 · Analysed npm/hawl.ai@0.1.14

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 13 packages
Packages resolved 13
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

The sandbox run completed and this package exposed no tools.

Install

How do I install the Hawl MCP server?

Hawl runs locally as an npm package, launched with npx -y hawl.ai. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · hawl.ai

# add to Claude Code
claude mcp add aaronlilla-hawl -- npx -y hawl.ai
Common questions

What is the Hawl MCP server?

Hawl is an MCP server listed in the public MCP registry as io.github.aaronlilla/hawl. Mailbox, handoffs and permits between your coding agents. Local mode needs no account. This page covers its npm package (hawl.ai).

Is the Hawl MCP server safe to use?

Hawl scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. It declares no install or post-install scripts. 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 Hawl MCP server expose?

Hawl exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the Hawl MCP server still maintained?

Hawl is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Hawl MCP server under?

Hawl declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.