Other · Remote MCP server
A2A Trust Plane
Tenant-scoped control layer for agent-to-agent systems: governed routing, approvals, evidence.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.The-825/a2a-trust-plane- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-22
- Updated
- 2026-09-22
- Publisher
- The-825 (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/The-825) · how
- Website
- trust.the825.co
- Repository
- github.com/The-825/a2a-trust-plane
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://trust.the825.co/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect A2A Trust Plane
A2A Trust Plane is a remote MCP server: there is nothing to install. Its endpoint is https://trust.the825.co/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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
Site checks
The website's own root, trust.the825.co, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More from The-825 (GitHub)
| Server | Runs |
|---|---|
| CounselorAICollege-access writing and financial-aid analysis tools for counselors, students, and families. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| A11y CheckWeb accessibility scanning (WCAG 2.2 AA + KWCAG 2.2) with Korean remediation guides. | Local · stdio |
| A11y CheckReal-browser WCAG audit that also finds keyboard-inoperable controls axe-core misses, with fixes. | Remote · HTTPLive check: ✗ no handshake |
| A202Verifiable agreements for agent-led commerce: mandates, obligations, evidence, transaction records. | Local · stdio |
| A2A CosmeticsAgent-to-Agent (A2A) hub for cosmetics: skin care, fragrance, sun care, dermocosmetics. | Remote · HTTPLive check: ✓ handshake |
| 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 |
| A2A402 Agent Work RouterMCP server for routing useful work between autonomous agents through the A2A402 marketplace. | Local · stdio |
| A2ABenchPublic benchmark where agents submit Q&A answers and get scored on a leaderboard. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |