io.github.hawthornhollows/passage-protocol
NPM · @CELLAR-DOOR/MCP-SERVER
Departure and admission records for AI agents with Ed25519/P-256 signatures.
Available components
Last scanned (20 hours ago)
Scores higher than 45% of npm servers
Category Security
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency22
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 234 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
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 4 Nov 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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
counter_sign_exit_marker ~70
Add a counter-signature to a signed EXIT marker, attesting agreement with the departure record
| Name | Type | Req | Description |
|---|---|---|---|
| markerJson | string | yes | JSON string of the signed EXIT marker to counter-sign |
| role | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| exitType | string | – | Type of exit (default: Voluntary) |
| origin | string | yes | DID or identifier of the departing agent |
| reason | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| exitMarkerJson | string | yes | JSON string of the EXIT marker |
| policy | string | yes | Admission 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.
| Name | Type | Req | Description |
|---|---|---|---|
| exitType | string | – | Type of exit (default: Voluntary) |
| origin | string | yes | DID or identifier of the departing agent |
| reason | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| admissionPolicy | string | – | Admission policy preset (default: OPEN_DOOR). Ignored if serverPolicy is set. |
| destination | string | yes | Destination platform/system identifier |
| exitMarkerJson | string | yes | JSON 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
| Name | Type | Req | Description |
|---|---|---|---|
| markerJson | string | yes | JSON 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
| Name | Type | Req | Description |
|---|---|---|---|
| arrivalMarkerJson | string | yes | JSON string of the ARRIVAL marker |
| exitMarkerJson | string | yes | JSON string of the EXIT marker |
No output schema declared.
No examples provided.
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
claude mcp add hawthornhollows-passage-protocol -- npx -y @cellar-door/mcp-server
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 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 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 4 November 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.