Walk the path insideCursor, Claude, VS Codeuntil a hop dies.

We walk search into fetch into write on the same MCP, then compare that chain across hosts. The failed step is the finding.

Cover your blind spots

search, then fetch, then write

fetch

write

CursorDied at write

VS CodeDied at fetch

CopilotFinished

The hop that died is the finding. Later steps stay untested.

A path is not a single call.

The first result has to become the next argument. That binding is the finding when it dies.

The path

Search, then fetch, then write. Stop where it breaks.

search → fetch → writePATH

Walk the path

The first call, then the call that needs the prior result. We show every action and each ID passed forward.

Runtime bindingCONFIRMED

search → { id: "c-12" }

↓ extract

fetch(id="c-12")

Stop at the failed step

That hop is the finding. Not a vague chain error. Later steps stay untested.

Same pathHOSTS

CursorDIED AT WRITE

VS CodeDIED AT FETCH

CopilotFINISHED

Compare the same path across hosts

Cursor finished. VS Code died on fetch. Same server. Same chain.

The binding

The first result has to become the next argument.

ChainBREAK

searchOK

fetchDIED

writeSTOPPED

A first call is not the job

Search can pass and fetch can die on the id that search returned.

HandoffHONEST

Earlier listEMPTY

Invented idNEVER

Named sourceTHEN FLAG

We do not invent ids

A later tool waiting on an empty earlier list is only a finding when a named earlier list supplied that id.

ReachSTOP

searchOK

fetchBROKE

writeUNTESTED

Later steps stay untested

The hop that died is the finding. Later steps stay untested.

The finding

The hop that died is the finding. No job is not a fail. This is not the host ledger.

JobN/A

Job set upNONE

This checkN/A

Server blamedNO

No job is not a fail

When no multi-step job is set up, this check does not apply. That is not a server failure.

ScopePATH

This pageTHE PATH

Host ledgerSEPARATE

Per-host rowTHERE

Not the host ledger

Host Compatibility can include the workflow row per host. This page is the path itself.

Binding

search → { id: "c-12" }

fetch(id="c-12")

Source into destination

Each ID is passed from its source step into its destination step. That binding is the finding when it dies.

FAQ

Common questions

Question	Answer
Is a completed first call enough?	No. The job is the chain. Search can pass and fetch can die on the id that search returned.
Do you invent ids?	No. A later tool waiting on an empty earlier list is only a finding when a named earlier list supplied that id. We do not invent one.
Is this the same as Host Compatibility?	Host Compatibility can include the workflow row per host. This page is the path itself: the hop that killed it, and the same path compared across hosts.

The first tool can passand the job still dies on the next hop.

Paste the MCP URL. We walk the chain and name the step that broke.

Cover your blind spots