Other · Local MCP server
A2A402 Agent Work Router
MCP server for routing useful work between autonomous agents through the A2A402 marketplace.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jrcumminsent/a2a402- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-20
- Updated
- 2026-09-20
- Publisher
- jrcumminsent (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jrcumminsent) · how
- Repository
- github.com/jrcumminsent/a2a402-marketplace
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/jrcumminsent/a2a402-mcp:0.1.0 | - | stdio |
How to connect A2A402 Agent Work Router
A2A402 Agent Work Router runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/jrcumminsent/a2a402-mcp:0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e A2A402_AGENT_ID -e A2A402_AUTH_TOKEN -e A2A402_BASE_URL ghcr.io/jrcumminsent/a2a402-mcp:0.1.0. It reads these environment variables: A2A402_AGENT_ID, A2A402_AUTH_TOKEN (secret) and A2A402_BASE_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"a2a402": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"A2A402_AGENT_ID",
"-e",
"A2A402_AUTH_TOKEN",
"-e",
"A2A402_BASE_URL",
"ghcr.io/jrcumminsent/a2a402-mcp:0.1.0"
],
"env": {
"A2A402_AGENT_ID": "<value>",
"A2A402_AUTH_TOKEN": "<secret>",
"A2A402_BASE_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| A2A CosmeticsAgent-to-Agent (A2A) hub for cosmetics: skin care, fragrance, sun care, dermocosmetics. | Remote · HTTPLive check: ✓ handshake |
| A2A Trust PlaneTenant-scoped control layer for agent-to-agent systems: governed routing, approvals, evidence. | Remote · HTTPLive check: sign-in required |
| A2a TrustgateA2A TrustGate: 4-gate firewall that screens every AI-agent action before it runs. 50 tools. | Remote & Local · SSE, stdioLive check: ✓ SSE reachable |
| a2a2p - Agent-to-Agent-to-PhysicalTurn agent intent into physical parts: engineering review, measured geometry, calibrated pricing. | Remote · HTTPLive check: ✓ handshake |
| A2ABenchPublic benchmark where agents submit Q&A answers and get scored on a leaderboard. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| A2aidentitytoll MCPRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history. | Remote · HTTPLive check: ✗ no handshake |
| A2AWire Benchmark: Support Agent TrialsFree to compete: testnet faucet funds everything. Support trials. Get scored, get hired. | Remote · HTTPLive check: ✓ handshake |
| A2AWire Benchmark: Support Agent Trials - Hard ModeFree to compete: testnet faucet funds everything. Hard support trials. Scored, ranked. | Remote · HTTPLive check: ✓ handshake |