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.

io.github.hawthornhollows/passage-protocol

NPM · @CELLAR-DOOR/MCP-SERVER · SCANNED SEP 20

Departure and admission records for AI agents with Ed25519/P-256 signatures.

Available components

npm · @cellar-door/mcp-server 77
0 this week 77 Trust /100
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 Security98
  • 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
  • 31 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency22
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 460 tokens (~51/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "verify_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 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
Install

How do I install the io.github.hawthornhollows/passage-protocol MCP server?

io.github.hawthornhollows/passage-protocol runs locally as an npm package, launched with npx -y @cellar-door/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @cellar-door/mcp-server

# add to Claude Code
claude mcp add hawthornhollows-passage-protocol -- npx -y @cellar-door/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "hawthornhollows-passage-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@cellar-door/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hawthornhollows-passage-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@cellar-door/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hawthornhollows-passage-protocol -- npx -y @cellar-door/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hawthornhollows-passage-protocol": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cellar-door/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hawthornhollows-passage-protocol --command npx --arg -y --arg @cellar-door/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  hawthornhollows-passage-protocol:
    command: "npx"
    args: ["-y", "@cellar-door/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hawthornhollows-passage-protocol": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cellar-door/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hawthornhollows-passage-protocol -t stdio -c npx -a -y @cellar-door/mcp-server
// mcp.json
{
  "mcpServers": {
    "hawthornhollows-passage-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@cellar-door/mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@cellar-door/mcp-server@0.1.7

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 105 packages
Packages resolved 105
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~460 tokens

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 →

Tool Tokens
counter_sign_exit_marker ~70

Add a counter-signature to a signed EXIT marker, attesting agreement with the departure record

NameTypeReqDescription
markerJsonstringyesJSON string of the signed EXIT marker to counter-sign
rolestring–Role label for the counter-signer (e.g. 'origin', 'platform')

No output schema declared.

No examples provided.

create_exit_marker ~67

Create and sign a departure marker. Uses session identity or generates a new one.

NameTypeReqDescription
exitTypestring–Type of exit (default: Voluntary)
originstringyesDID or identifier of the departing agent
reasonstring–Human-readable reason for departure

No output schema declared.

No examples provided.

evaluate_admission ~48

Check whether an EXIT marker meets an admission policy without creating an arrival

NameTypeReqDescription
exitMarkerJsonstringyesJSON string of the EXIT marker
policystringyesAdmission policy preset

No output schema declared.

No examples provided.

generate_identity ~22

Generate a new Ed25519 DID keypair for signing EXIT markers

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_admission_policies ~20

List available admission policy presets and their configurations

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quick_exit ~67

One-shot create and sign a departure marker. Generates a new identity if none exists.

NameTypeReqDescription
exitTypestring–Type of exit (default: Voluntary)
originstringyesDID or identifier of the departing agent
reasonstring–Human-readable reason for departure

No output schema declared.

No examples provided.

verify_and_admit ~78

Verify an EXIT marker, evaluate an admission policy, and create a signed arrival marker

NameTypeReqDescription
admissionPolicystring–Admission policy preset (default: OPEN_DOOR). Ignored if serverPolicy is set.
destinationstringyesDestination platform/system identifier
exitMarkerJsonstringyesJSON string of the EXIT marker

No output schema declared.

No examples provided.

verify_exit_marker ~35

Verify a signed EXIT marker from its JSON representation

NameTypeReqDescription
markerJsonstringyesJSON string of the EXIT marker to verify

No output schema declared.

No examples provided.

verify_transfer ~53

Verify a complete EXIT→ENTRY transfer: check both markers and continuity

NameTypeReqDescription
arrivalMarkerJsonstringyesJSON string of the ARRIVAL marker
exitMarkerJsonstringyesJSON string of the EXIT marker

No output schema declared.

No examples provided.

Common questions

What is the io.github.hawthornhollows/passage-protocol MCP server?

io.github.hawthornhollows/passage-protocol is an MCP server listed in the public MCP registry as io.github.hawthornhollows/passage-protocol. Departure and admission records for AI agents with Ed25519/P-256 signatures. This page covers its npm package (@cellar-door/mcp-server).

Is the io.github.hawthornhollows/passage-protocol MCP server safe to use?

io.github.hawthornhollows/passage-protocol scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.hawthornhollows/passage-protocol MCP server expose?

io.github.hawthornhollows/passage-protocol exposes 9 tools: generate_identity, quick_exit, create_exit_marker, verify_exit_marker, counter_sign_exit_marker, and 4 more. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

Is the io.github.hawthornhollows/passage-protocol MCP server still maintained?

io.github.hawthornhollows/passage-protocol is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.hawthornhollows/passage-protocol MCP server under?

io.github.hawthornhollows/passage-protocol 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.