# passalong Hand tasks, bugs and finished work to AI coding agents, and get back a write-up with evidence. - **Type:** MCP server - **Trust:** 85/100 (A), scored on the package rubric - **Verification:** verified (build provenance) - **Version:** 0.17.0 - **Author:** Lukman Isiaka - **License:** MIT - **npm:** passalong - **Endpoints:** streamable-http https://passalong.dev/v1/mcp - **Source:** https://github.com/codellyson/passalong - **Endpoint health:** reachable (last checked 2026-10-11T15:37:21.079Z, 1 sample) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 85/100 (A), scored on the package rubric - Publisher verified: no - Build provenance: verified attestation - npm trusted publishing (OIDC): yes - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-10-11T15:37:01.826Z - **Version scanned:** 0.17.0 - **CVEs:** none found by OSV at scan time ## Tools 38 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `assign` — Reassign a guide or task the user wrote, or one assigned to them, to someone else in its team, when the user asks: - `list_folders` — Find project folders of documents, assets and guides. Pass query to find the folders whose name, description, or any document's name or text mention those words - `create_folder` — Create a folder or nested subfolder after checking list_folders. Pass parent to nest it; omit team for a private root, and pass a team slug only when sharing wa - `update_folder` — Rename, describe, recolor or move a folder. Pass parent as an empty string to move it to the top level. A folder cannot move inside itself or a descendant, or i - `get_folder` — List a folder's documents, assets and linked guides. - `get_folder_document` — Read the full Markdown and version before editing it. - `get_folder_asset` — Read an image or small text file from a folder into this agent's context. Other file types stay private downloads. - `add_folder_asset` — Add a screenshot, reference file or other asset from this machine to a folder. Use a real file path you can read; the bytes are uploaded directly, not copied in - `create_folder_document` — Add Markdown such as a brief or script to a folder. - `save_folder_document` — Save a new revision. Send the version returned when you read it; a newer edit is refused. - `rename_folder_document` — Rename a folder document. Its id, text and history stay; no version is needed, because a rename cannot overwrite anyone's text. - `get_folder_document_history` — Read a folder document's earlier versions. Without version, lists them newest first; with version, returns that version's text. To bring one back, save it with - `link_folder_guide` — Put a task, bug or handoff guide in the folder, beside the documents and assets it uses: one just published or one that already existed. - `unlink_folder_guide` — Take a guide out of a folder. Only the link goes: the guide itself is unchanged, and link_folder_guide puts it back. - `delete_folder_document` — Delete one document from a folder, with its earlier versions. It cannot be brought back, so do it only when the person asked for that document to go; to change - `delete_folder_asset` — Delete one file from a folder. It cannot be brought back, so do it only when the person asked for that file to go. - `search_guides` — Search transfer guides by words in the title, tags, stack, or body: the user's own - `inbox` — Guides handed to this user (or to their teams) that they have not pulled yet. Call it - `board` — The state of this user's transfers as queues: waiting on you (handed to you, not - `log` — This user's own acts on guides, newest first: what they published, what they took - `activity` — What has happened to this user's guides and handoffs: who pulled one, who archived one, - `clear_activity` — Clear the user's unread feed, after they have been shown what is in it. Read it with - `plan_tasks` — Write tasks for agents: one step for a single task, or a larger goal broken into steps - `take` — Say you are doing it, and get it. With `id`, that guide — any kind: a task, a bug, a - `progress` — Say you are still on what you hold, with a one-line note the hub shows. 30 minutes - `hand_in` — Done here, with proof, sorted against the line it answers. Send `checks`: one entry per - `ask` — You need the person's answer before you can go on. Ask one clear question, with the - `pass` — Not yours to do, or you are stuck: give it back with the reason. It is open again for - `get_guide` — READ a transfer guide by passalong id or share link and return its markdown. A guide over - `attach_screenshot` — Upload an image as evidence — a path in `file`, or the bytes in `data` when you have - `attach_file` — Upload a file that is not a picture — a log, a PDF, a CSV, a zip, up to 10MB — and get - `reply` — A person's tool, for someone driving their work from an assistant: write to whoever - `publish_guide` — Publish a guide from markdown (frontmatter + sections). Check what you hold first (take - `file_bugs` — File one or more bugs you found but are not fixing, as a set. Opens a report and - `guide_template` — The empty guide skeleton with guidance comments for each section. By default a task - `accounts` — The Passalong accounts signed in on this machine, which one this session is using, and - `use_account` — Say which signed-in account this session acts as. Call it only with a name the PERSON - `set_guide_status` — Archive a guide (`consumed`) or put it back on the board (`published`). Archiving is the ## Install **Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"passalong\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"passalong\"\n ]\n }\n }\n}" ``` ## Blast radius Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs locally and hosted. - Floor 42, ceiling 66 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/passalong - Install plan: https://forgeregistry.com/api/v1/packages/passalong/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/passalong - HTML page: https://forgeregistry.com/registry/passalong - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.