Scan MCP Online API Star

A2a (GongRzhe) MCP Server

a2a-mcp-server PyPI v0.1.5

Published by gongrzhe — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A bridge server that connects Model Context Protocol (MCP) with Agent-to-Agent (A2A) protocol

View on PyPI ↗ Repository ↗ Raw report (JSON) ↗
Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 96 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 3.6 = 96. What the published surface and source actually contain:

PointsWhat was foundCategory
−3.6 Near-miss of exa-mcp-server MTC-SUP-005 supply-chain

2. Client adoption risk — 96 − 4 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Near-miss of exa-mcp-server (edit distance 2)MTC-SUP-005

"a2a-mcp-server" is edit-distance 2 from the package "exa-mcp-server". Verify this is the intended package.

Fix: Confirm you meant "exa-mcp-server". Install packages only from their documented, official name.

Location: package a2a-mcp-server

Tools 7

Each tool and what it can reach — statically extracted from the published source.

  • send_messagenetwork egress
  • send_message_streamnetwork egress
  • cancel_taskno sensitive capability
  • get_task_resultno sensitive capability
  • list_agentsno sensitive capability
  • register_agentno sensitive capability
  • unregister_agentno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.5 latest A 92/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/a2a-mcp-server-2/badge.svg)](https://mcptrustchecker.com/registry/a2a-mcp-server-2)
HTML
<a href="https://mcptrustchecker.com/registry/a2a-mcp-server-2"><img src="https://mcptrustchecker.com/registry/a2a-mcp-server-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/a2a-mcp-server-2/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan a2a-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of A2a 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

A2a (npm) npm
A
a2a-mcp-server

MCP server for Agent-to-Agent (A2A) protocol integration

AI & Agents Score 91/100 2 findings 18/wk Cap. Moderate

More in AI & Agents

Agent Source verified npm
A
@aauth/mcp-agent

Authenticated MCP transport with HTTP Signatures for AAuth agents

AI & Agents Score 100/100 1 finding 1.4k/wk Cap. Minimal
Agent Claim Source verified npm
A
@vk0/agent-claim-mcp

Local-first MCP server for parallel AI coding agents to claim file ownership before edits, preventing stomping on each other in the same worktree.

AI & Agents Score 100/100 0 findings 66/wk Cap. Minimal
Agent Comm Source verified npm
A
agent-comm

Agent-agnostic intercommunication system — sessions, messaging, channels, shared state, and real-time events

AI & Agents Score 100/100 2 findings 159/wk Cap. Minimal
Agent Comm Source verified npm
A
@jerfowler/agent-comm-mcp-server

MCP server for AI agent task communication and delegation with diagnostic lifecycle visibility

AI & Agents Score 100/100 0 findings 17/wk Cap. Minimal
Agent Mcp Manager Source verified npm
A
agent-mcp-manager

Programmatic add/link/unlink for MCP servers across 23 AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Zed, Cline, OpenCode, Goose, Kiro, Windsurf, and more). Functional API with dry-run support.

AI & Agents Score 100/100 0 findings 234/wk Cap. Minimal
Agent Mesh Source verified npm
A
@reaatech/agent-mesh-mcp-server

MCP server layer exposing agent-mesh orchestrator as an MCP agent

AI & Agents Score 100/100 0 findings 9/wk Cap. Minimal