reaatech/a2a-reference-ts

MCPcommunity
reaatechMITUpdated 3mo agoGitHub

Enterprise-grade TypeScript implementation of Google's Agent-to-Agent (A2A) protocol with a bidirectional A2A ↔ MCP bridge, OAuth2/JWT auth, Redis/Postgres persistence, SSE streaming, and OpenTelemetry observability.

Production-ready TypeScript reference implementation of the Agent-to-Agent (A2A) protocol — server framework, client SDK, CLI scaffolding, and a bidirectional A2A ↔ MCP bridge. The A2A protocol defines how AI agents discover each other, exchange messages, and manage task lifecycles. This project provides the canonical TypeScript implementation — battle-tested Zod schemas, pluggable server…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
3mo agoLast update
Package
Authorreaatech
LicenseMIT
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface9 tools · 1 privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · 1 privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

read_fileNo description published

This tool published no description. Forge does not invent one.

write_fileprivilegedNo description published

This tool published no description. Forge does not invent one.

calculateNo description published

This tool published no description. Forge does not invent one.

screenshotNo description published

This tool published no description. Forge does not invent one.

bad_toolNo description published

This tool published no description. Forge does not invent one.

tool_aNo description published

This tool published no description. Forge does not invent one.

tool_bNo description published

This tool published no description. Forge does not invent one.

audioNo description published

This tool published no description. Forge does not invent one.

resultNo description published

This tool published no description. Forge does not invent one.

0 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Production-ready TypeScript reference implementation of the Agent-to-Agent (A2A) protocol — server framework, client SDK, CLI scaffolding, and a bidirectional A2A ↔ MCP bridge. The A2A protocol defines how AI agents discover each other, exchange messages, and manage task lifecycles. This project provides the canonical TypeScript implementation — battle-tested Zod schemas, pluggable server adapters, a type-safe client, and infrastructure for authentication, persistence, observability, and push…

Keywords
a2aagent-orchestrationagent-to-agentagentic-aiai-agentsexpressgoogle-a2ahonollm-toolsmcpmcp-bridgemodel-context-protocolmonorepomulti-agentoauth2opentelemetrypostgresredisssetypescript
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in databases