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.

IAF Agent Bridge

NPM · IAF-AGENT-BRIDGE

MCP server that sends work to Cursor Agent over ACP and returns the session id needed to continue.

Available components

−1 this week 74 Trust /100

Last scanned (17 hours ago)

Scores higher than 52% of npm servers

Category Developer Tools

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 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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 20 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 792 tokens (~264/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 4 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
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.

  • 24 Oct 26 −4
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 +3
    • Security disclosure: pass → unverified ▼ 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 24 Oct 2026 · Analysed npm/iaf-agent-bridge@1.1.0

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 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~495 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
cancel ~77

Cancel an in-flight Cursor turn by sessionId. Status is cancelled, killed, not-running (the turn ended and the session can still be resumed), or not-found.

NameTypeReqDescription
forceboolean–After a short grace period, kill the Cursor process if the turn is still running.
sessionIdstringyesSession id returned by delegate.

No output schema declared.

No examples provided.

delegate ~348

Send a prompt to Cursor Agent and wait until that Cursor turn is terminal, including tool work and any sub-agent follow-up Cursor performs before it stops. Returns Cursor's reply and the sessionId to reuse. A second call for a session that is still running is rejected. You decide CONTINUE, COMPLETE, or BLOCKED. Do not shell out to the agent binary.

NameTypeReqDescription
contextstring–Context-window option when the model advertises one, such as 272k or 1m. Omit unless the user asks.
contextFilesarray–Files to attach. Text becomes resource links. Images (png, jpg, gif, webp, under 5MB) are sent inline when Cursor accepts them. Missing files are warnings, not failures.
effortstring–Exact effort value advertised by the selected model. Invalid values fail before the prompt and name the accepted set.
fastboolean–Request Cursor's fast tier. Leave false unless the user asks. Higher cost.
modestring–agent implements. plan asks Cursor to produce a plan and stop. ask is for a read-oriented question. The mode is an instruction to Cursor.
modelstring–Optional Cursor model id. Omit to keep Cursor's current default.
promptstringyesNatural prompt for Cursor. Sent as written. Point at files and project documents instead of pasting them.
sessionIdstring–Resume this Cursor session. Omit to start one. Use the sessionId from the previous result for follow-up work.
workspacestringyesExisting project directory Cursor will work in. Must not be the home directory or filesystem root.

No output schema declared.

No examples provided.

doctor ~70

Report Node, bridge version, Cursor CLI discovery, authentication state without secrets, and an optional ACP handshake.

NameTypeReqDescription
deepboolean–Open a short ACP session to verify Cursor can start. This creates an empty Cursor session.
workspacestring–Optional project directory to validate and scan for project context files.

No output schema declared.

No examples provided.

Install

How do I install the IAF Agent Bridge MCP server?

IAF Agent Bridge runs locally as an npm package, launched with npx -y iaf-agent-bridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · iaf-agent-bridge

# add to Claude Code
claude mcp add francescoveryra-dot-iaf-agent-bridge -- npx -y iaf-agent-bridge
Common questions

What is the IAF Agent Bridge MCP server?

IAF Agent Bridge is an MCP server listed in the public MCP registry as io.github.francescoveryra-dot/iaf-agent-bridge. MCP server that sends work to Cursor Agent over ACP and returns the session id needed to continue. This page covers its npm package (iaf-agent-bridge).

Is the IAF Agent Bridge MCP server safe to use?

IAF Agent Bridge scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 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 IAF Agent Bridge MCP server expose?

IAF Agent Bridge exposes 3 tools: delegate, cancel, doctor. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.

Is the IAF Agent Bridge MCP server still maintained?

IAF Agent Bridge is still listed as active in the MCP registry. We last reached this channel on 24 October 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 IAF Agent Bridge MCP server under?

IAF Agent Bridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.