MCP.Market

Passalong MCP server

online · 100% uptime
by codellyson·io.github.codellyson/passalong·v0.13.1

Hand tasks, bugs and finished work to AI coding agents, and get back a write-up with evidence.

A98/100grade A
What users say
No reviews yet
Be the first
Safety scan
A98/100

full report

Adoption
Growing

0 stars607 downloads/wk

Reviews

Write one

Nobody has reviewed Passalong yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Passalong tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan10 source files scanned25/25
  • Live reliabilityremote reachable in 306ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 98/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Passalong compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
98/100
higher than 99% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
373 ms
faster than 39% of 30,031 servers
Downloads a week
607
more than 90% of 12,191 servers with a package

Install Passalong in Claude Code, Cursor or VS Code

claude mcp add --transport http passalong https://passalong.dev/v1/mcp
Add to Cursor

What the publisher says

From the Passalong repository's README, as published. We do not edit it. Read it on GitHub

Passalong

Hand work to your AI coding agents, and get back what they did and how they checked it.

Write a task, a bug or a finished change once. The agent that takes it starts knowing what done looks like and what was already decided, reports as it goes, and hands back a write-up with the evidence for each thing you asked for, which you approve or send back. One agent per job, and everyone can see who has what. Works with Claude Code, Codex, ChatGPT, Claude, or anything that speaks MCP or HTTP. See passalong.dev.

npm i -g passalong
passalong setup      # installs the Claude Code capture skill, the MCP server, two hooks and a status line
passalong login      # optional: sync guides across machines and get share links
codex mcp add passalong -- passalong mcp   # Codex: the same MCP server

The loop

run passalong share yourself.

  1. Finish work in Claude Code (or any agent). Say "pass this along", run /passalong-capture, or

agent with the Passalong MCP server. The guide lands in its context; it implements, adapting the parts marked ASSUMES:.

  1. Trim and publish. The draft opens in your editor. Save it and you get a short id and a link.
  2. Pull on the other side. passalong pull in the target repo, or paste the link to any

passalong done shelves it when you are finished with it.

  1. Close. Say whether it worked: passalong works , or passalong broken .

Commands

passalong share [file] [--to team[/handle]]  publish a guide → id + link; --to hands it to a team or teammate
passalong task "<what needs doing>"  write a task for an agent; it waits in Draft
passalong ready <id...|--all> tasks you have read are ready — an agent may take them now
passalong tasks               every task and where it is: draft, ready, claimed, stalled, review
passalong work [--once] [--agent CMD]  run an agent on each ready task here, one after another
passalong approve <id>        the work in review is done
passalong reject <id> <why>   not done: back to Ready, and the next agent reads why
passalong release <id>        take a task back from the agent holding it, stalled or not
passalong pull <id|link>      fetch a guide into ./.passalong/ (git-ignored) and print it
passalong inbox               guides handed to you that you have not pulled yet
passalong board               waiting on you, in flight, landed, worth keeping
passalong activity [--all]    what happened while you were away; clears unless --all
passalong log [repo]          what you did, newest first, under a heading per month
passalong list [query]        your guides and your teams', local and synced
pas

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Passalong: common questions

Is Passalong MCP server safe?
Yes, by our scan: it is graded A (98/100). Read the Passalong safety report
How do I install Passalong?
It runs remotely at passalong.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Passalong need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Passalong maintained?
The last commit was 32 days ago (2026-10-03). The latest release is v0.13.1.
Is Passalong up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Passalong compare with other MCP servers?
safety score 98/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 373 ms (faster than 39% of 30,031 servers). Full comparison.