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.

A2AWire

REMOTE · A2AWIRE.COM · 2 COMPONENTS

Escrow, reputation, and payments for agent-to-agent commerce. Non-custodial USDC/Base L2.

+4 this week 39 Trust /100

Last scanned (1 hour ago)

Scores higher than 35% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 5 Nov 26 +4
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 2 Nov 26 −4
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Capabilities: pass → unverified ▼ functional
  • 1 Nov 26 +4
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 31 Oct 26 −4
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Capabilities: pass → unverified ▼ functional
  • 30 Oct 26 +4
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 28 Oct 26 −4
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Capabilities: pass → unverified ▼ functional
  • 27 Oct 26 +4
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 22 Oct 26 −44
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ 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 5 Nov 2026 · Probed https://a2awire.com/mcp/http

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=a2awire.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 12 Jun 2026 26 Dec 2026 RSA 2048 SHA256-RSA ceeeab5f7536fc4b9dba79ae6d8ee22
SANs: a2awire.com, *.a2awire.com, a2awire.io, *.a2awire.io
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of a2awire.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
a2awire.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://a2awire.com/mcp/http Verified 200
http (plaintext) http://a2awire.com/mcp/http HTTPS enforced 301 https://a2awire.com/mcp/http
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the A2AWire MCP server?

A2AWire is a hosted endpoint at https://a2awire.com/mcp/http, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · a2awire.com

# add to Claude Code
claude mcp add --transport http com-a2awire-a2awire 'https://a2awire.com/mcp/http'
Common questions

What is the A2AWire MCP server?

A2AWire is an MCP server listed in the public MCP registry as com.a2awire/a2awire. Escrow, reputation, and payments for agent-to-agent commerce. Non-custodial USDC/Base L2. This page covers its hosted endpoint (https://a2awire.com/mcp/http).

Is the A2AWire MCP server safe to use?

A2AWire scores 39 out of 100 on VerifyMCP. 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.

Does the A2AWire MCP server require authentication?

No. We connected to A2AWire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the A2AWire MCP server still maintained?

A2AWire is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.