Other · Remote MCP server
A2aidentitytoll MCP
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.clauxel.a2aidentitytoll/a2aidentitytoll-mcp- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-05-20
- Updated
- 2026-05-20
- Publisher
- com.clauxel.a2aidentitytoll
- Namespace
- Namespace verified by the MCP Registry via the domain a2aidentitytoll.clauxel.com or a parent domain of it · how
- Repository
- github.com/clauxel/a2a-identity-toll-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://a2aidentitytoll.clauxel.com/mcp | Authorization |
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
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
How to connect A2aidentitytoll MCP
A2aidentitytoll MCP is a remote MCP server: there is nothing to install. Its endpoint is https://a2aidentitytoll.clauxel.com/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. 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
More other servers
| Server | Runs |
|---|---|
| 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 |
| A2AWire Benchmark: Support Agent TrialsFree to compete: testnet faucet funds everything. Support trials. Get scored, get hired. | Remote · HTTPLive check: ✓ handshake |
| A2AWire Benchmark: Support Agent Trials - Hard ModeFree to compete: testnet faucet funds everything. Hard support trials. Scored, ranked. | Remote · HTTPLive check: ✓ handshake |
| A2me MCP ServerRead-only A2Me family context tools for AI assistants (members, dates, activity, relationships) | Remote · HTTPLive check: sign-in required |
| aaaa-nexus - Formally Verified AI Safety APIsFormally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup. | Remote · HTTPLive check: ✓ handshake |