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.

io.github.mdfifty50-boop/a2a-bridge

NPM · A2A-BRIDGE-MCP · SCANNED SEP 25

Agent-to-agent communication bridge for multi-agent systems

Available components

0 this week 75 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability45
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 557 tokens (~61/item across 9 items; 8 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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 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; "broadcast_task" implies "send" 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
Install

How do I install the io.github.mdfifty50-boop/a2a-bridge MCP server?

io.github.mdfifty50-boop/a2a-bridge runs locally as an npm package, launched with npx -y a2a-bridge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · a2a-bridge-mcp

# add to Claude Code
claude mcp add mdfifty50-boop-a2a-bridge -- npx -y a2a-bridge-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mdfifty50-boop-a2a-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "a2a-bridge-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mdfifty50-boop-a2a-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "a2a-bridge-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mdfifty50-boop-a2a-bridge -- npx -y a2a-bridge-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mdfifty50-boop-a2a-bridge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "a2a-bridge-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mdfifty50-boop-a2a-bridge --command npx --arg -y --arg a2a-bridge-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mdfifty50-boop-a2a-bridge:
    command: "npx"
    args: ["-y", "a2a-bridge-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mdfifty50-boop-a2a-bridge": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "a2a-bridge-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mdfifty50-boop-a2a-bridge -t stdio -c npx -a -y a2a-bridge-mcp
// mcp.json
{
  "mcpServers": {
    "mdfifty50-boop-a2a-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "a2a-bridge-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

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

  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 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 25 Sept 2026 · Analysed npm/a2a-bridge-mcp@0.1.1

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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~553 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
broadcast_task ~110

Send a task to ALL agents matching a capability. Creates individual tasks for each match for aggregation.

NameTypeReqDescription
capability_neededstringyesCapability to match agents against
from_agentstringyesAgent ID of the broadcaster
input_dataobject–Input data for the task
min_scorenumber–Minimum capability match score (default 0.3)
task_descriptionstringyesWhat matched agents should do
timeout_msinteger–Timeout per agent in milliseconds

No output schema declared.

No examples provided.

delegate_task ~104

Delegate a task to a specific registered agent. Creates a tracked task with status lifecycle (pending -> running -> completed/failed).

NameTypeReqDescription
from_agentstringyesAgent ID of the delegator
input_dataobject–Input data for the task
task_descriptionstringyesWhat the target agent should do
timeout_msinteger–Timeout in milliseconds (default 30s)
to_agentstringyesAgent ID of the target agent

No output schema declared.

No examples provided.

discover_agents ~57

Find registered agents matching a capability need. Returns scored results with fuzzy text matching.

NameTypeReqDescription
capability_neededstringyesCapability to search for
min_scorenumber–Minimum similarity score (0-1, default 0.3)

No output schema declared.

No examples provided.

get_agent_card ~42

Get an agent's full capability card — capabilities, schemas, stats. Inspired by Google A2A agent cards.

NameTypeReqDescription
agent_idstringyesAgent identifier

No output schema declared.

No examples provided.

get_task_result ~76

Get status/result of a delegated task. Executing agents call this with submit_result or submit_error to report completion.

NameTypeReqDescription
submit_errorstring–Submit failure error message
submit_resultobject–Submit completion result (called by executing agent)
task_idstringyesTask ID from delegate_task or broadcast_task

No output schema declared.

No examples provided.

health_check ~20

Returns server health, uptime, version, and call stats

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_agents ~38

List all registered agents. Optionally filter by a capability keyword.

NameTypeReqDescription
filterstring–Capability keyword to filter by (empty = show all)

No output schema declared.

No examples provided.

register_agent ~106

Register an agent with its capabilities, input/output schemas for discovery by other agents.

NameTypeReqDescription
agent_idstringyesUnique identifier for the agent
capabilitiesarrayyesCapability strings (e.g. ["code-review", "summarization"])
descriptionstring–Human-readable description
endpointstring–Optional endpoint or transport hint
input_schemaobject–JSON schema for accepted input
output_schemaobject–JSON schema for produced output

No output schema declared.

No examples provided.

Common questions

What is the io.github.mdfifty50-boop/a2a-bridge MCP server?

io.github.mdfifty50-boop/a2a-bridge is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/a2a-bridge. Agent-to-agent communication bridge for multi-agent systems. This page covers its npm package (a2a-bridge-mcp).

Is the io.github.mdfifty50-boop/a2a-bridge MCP server safe to use?

io.github.mdfifty50-boop/a2a-bridge scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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.mdfifty50-boop/a2a-bridge MCP server expose?

io.github.mdfifty50-boop/a2a-bridge exposes 8 tools: health_check, register_agent, discover_agents, delegate_task, get_task_result, and 3 more. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.

Is the io.github.mdfifty50-boop/a2a-bridge MCP server still maintained?

io.github.mdfifty50-boop/a2a-bridge is still listed as active in the MCP registry. We last reached this channel on 25 September 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.mdfifty50-boop/a2a-bridge MCP server under?

io.github.mdfifty50-boop/a2a-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.