Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.
Warning

Malware flagged

A supply-chain scanner flagged a high-severity malware risk in another channel of this server. Treat this server as unsafe to install until the finding is cleared.

Flagged channel: npm · a2a-trustgate

io.github.jyswee/a2a-trustgate

REMOTE · MCP.A2AINFRASTRUCTURE.COM · 2 COMPONENTS · SCANNED AUG 3

A2A TrustGate: 4-gate firewall that screens every AI-agent action before it runs. 49 tools.

+2 this week 60 Trust /100
Trust breakdown (6 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 →

Endpoint Security57
Transport & Reachability40
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 188 tokens (~94/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.a2ainfrastructure.com

# add to Claude Code
claude mcp add --transport http jyswee-a2a-trustgate https://mcp.a2ainfrastructure.com/sse
# ~/.codex/config.toml
[mcp_servers.jyswee-a2a-trustgate]
url = "https://mcp.a2ainfrastructure.com/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jyswee-a2a-trustgate": {
      "type": "remote",
      "url": "https://mcp.a2ainfrastructure.com/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jyswee-a2a-trustgate --url https://mcp.a2ainfrastructure.com/sse --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jyswee-a2a-trustgate:
    url: "https://mcp.a2ainfrastructure.com/sse"
// mcp.json
{
  "mcpServers": {
    "jyswee-a2a-trustgate": {
      "type": "http",
      "url": "https://mcp.a2ainfrastructure.com/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 58

    First indexed and scored.

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 3 Aug 2026 · Probed https://mcp.a2ainfrastructure.com/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=a2ainfrastructure.com CN=YR2,O=Let's Encrypt,C=US 11 Jul 2026 9 Oct 2026 RSA 4096 SHA256-RSA 591a2232dd663960318bc7b6221c84433a4
SANs: *.a2ainfrastructure.com, a2ainfrastructure.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of mcp.a2ainfrastructure.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
a2ainfrastructure.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 404
Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.a2ainfrastructure.com/sse Verified 200
http (plaintext) http://mcp.a2ainfrastructure.com/sse HTTPS enforced 301 https://mcp.a2ainfrastructure.com/sse
MCP tools — 2 exposed · ~188 tokens

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.

Tool Tokens
a2a_get_started ~36

Explains what A2A TrustGate is and how to activate this MCP server (no API key on this session yet).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

a2a_signup ~152

Create a new A2A TrustGate tenant and get an API key (shown once), unlocking all safety tools in this session immediately. Agent-first: only a short tenant slug is required — no email or password. A human must then add a card (secure Stripe checkout) at the returned paymentUrl to activate; /v1 calls return 402 until activated.

NameTypeReqDescription
agentstringAgent/label creating the tenant (optional, e.g. "claude-code")
descriptionstringWhat this tenant is for (optional)
tenantIdstringyesShort tenant slug, 3-64 chars, lowercase alphanumeric + hyphens (e.g. "my-agent")

No output schema declared.

No examples provided.