A2A Trust Plane

io.github.The-825Published by GitHub account The-825v0.1.0Updated Oct 27, 2026

Tenant-scoped control layer for agent-to-agent systems: governed routing, approvals, evidence.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant a tenant-scoped control layer for agent-to-agent systems: governed routing, approvals and evidence.

What you can do
  • Governed routing of agent-to-agent requests within a tenant scope.
  • Approval handling for agent actions that need sign-off.
  • Evidence capture around agent-to-agent interactions.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Worth considering when you run multi-agent or agent-to-agent systems and want routing, approvals and evidence handled by a shared control plane rather than ad hoc in each agent.
Requirements
A remote streamable HTTP endpoint; no local package. Authentication is required: an Authorization header carrying a bearer token, either an operator key from the deployment's A2A_TRUST_API_KEYS or a short-lived trial credential issued at the provider's trial page. OAuth is declared as required.
Before you install
The Authorization bearer token is a secret with operator-level access; keep it out of logs and shared configs. Trial credentials are short-lived, so plan for a real operator key. The server sits in the path of agent-to-agent traffic and handles approvals and evidence, so review what it records and who can approve before relying on it.

Installation

In SourceWeft

  1. Open A2A Trust Plane in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.The-825%2Fa2a-trust-plane/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "a2a-trust-plane": {
      "type": "http",
      "url": "https://trust.the825.co/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 22, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.