io.github.mdfifty50-boop/a2a-bridge
NPM · A2A-BRIDGE-MCP
Agent-to-agent communication bridge for multi-agent systems
Available components
Last scanned (20 hours ago)
Scores higher than 44% of npm servers
Category AI and Machine Learning
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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 210 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 16 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 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.
- 8 Nov 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.87 functional
- 7 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
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 21 Nov 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 →
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 | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
broadcast_task ~110
Send a task to ALL agents matching a capability. Creates individual tasks for each match for aggregation.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_needed | string | yes | Capability to match agents against |
| from_agent | string | yes | Agent ID of the broadcaster |
| input_data | object | – | Input data for the task |
| min_score | number | – | Minimum capability match score (default 0.3) |
| task_description | string | yes | What matched agents should do |
| timeout_ms | integer | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| from_agent | string | yes | Agent ID of the delegator |
| input_data | object | – | Input data for the task |
| task_description | string | yes | What the target agent should do |
| timeout_ms | integer | – | Timeout in milliseconds (default 30s) |
| to_agent | string | yes | Agent 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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_needed | string | yes | Capability to search for |
| min_score | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent 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.
| Name | Type | Req | Description |
|---|---|---|---|
| submit_error | string | – | Submit failure error message |
| submit_result | object | – | Submit completion result (called by executing agent) |
| task_id | string | yes | Task 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.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Unique identifier for the agent |
| capabilities | array | yes | Capability strings (e.g. ["code-review", "summarization"]) |
| description | string | – | Human-readable description |
| endpoint | string | – | Optional endpoint or transport hint |
| input_schema | object | – | JSON schema for accepted input |
| output_schema | object | – | JSON schema for produced output |
No output schema declared.
No examples provided.
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
claude mcp add mdfifty50-boop-a2a-bridge -- npx -y a2a-bridge-mcp
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 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 21 November 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.
What did VerifyMCP test on the io.github.mdfifty50-boop/a2a-bridge MCP server?
VerifyMCP ran 16 checks on io.github.mdfifty50-boop/a2a-bridge, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.