Hosted MCP server/Development

A2A Trust Plane MCP server

Hosted at trust.the825.co·Streamable HTTP

A2A Trust Plane provides governed agent handoffs, approval checks and completion evidence. The connection uses a provider-issued TRUST_PLANE_TOKEN scoped to one tenant and a defined skill set, not a generic API key. Completion evidence is separately gated: evidence:run must be provisioned explicitly with support and is not implied by an account or paid plan. A read-only check should use city_catalog or city_quote; an execution may consume one governed operation from the plan.

trust.the825.co Streamable HTTP Provider-issued agent credential (TRUST_PLANE_TOKEN), scoped to one tenant and skill set Server not checked yet Reviewed 2026-11-16
About

Where it fits

Teams coordinating multi-agent workflows that need approval gates and auditable completion evidence.

  • Read the city catalog or a quote without consuming an operation.
  • Hand off a task with approval checks.
  • Record completion evidence after evidence:run is provisioned.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds A2A Trust Plane as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http a2a-trust-plane https://trust.the825.co/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://trust.the825.co/mcp
Host
trust.the825.co · /mcp
Transport
Streamable HTTP
Authentication
Provider-issued agent credential (TRUST_PLANE_TOKEN), scoped to one tenant and skill set
Server name
a2a-trust-plane
Listing type
Community or directory listing

The installer uses the server name a2a-trust-plane. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that a2a-trust-plane appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Read the city catalog or a quote without consuming an operation. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

A2A Trust Plane documentationhttps://trust.the825.co/docs