Developer · Remote MCP server
A2adependencyinspector MCP
Remote MCP for A2A dependency inspector MCP, structured receipts, audit logs, and reviewer-ready evi.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.clauxel.a2adependencyinspector/a2adependencyinspector-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-20
- Updated
- 2026-05-20
- Publisher
- com.clauxel.a2adependencyinspector
- Namespace
- Namespace verified by the MCP Registry via the domain a2adependencyinspector.clauxel.com or a parent domain of it · how
- Repository
- github.com/clauxel/a2a-dependency-inspector-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://a2adependencyinspector.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 A2adependencyinspector MCP
A2adependencyinspector MCP is a remote MCP server: there is nothing to install. Its endpoint is https://a2adependencyinspector.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 developer servers
| Server | Runs |
|---|---|
| 4da MCP ServerUpgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans. | Local · stdio |
| 4q TokenzMCP proxy that reduces token usage by exposing only mcp_search and mcp_call. | Local · stdio |
| 7IT SolutionsStore speed, web-app security checks, automation ROI, checklists and guides from 7IT Solutions. | Remote · HTTPLive check: ✓ handshake |
| A2a AuditorScans Agent2Agent (A2A) protocol code for webhook SSRF, missing auth, and credential exposure. | Local · stdio |
| A2ahubReliable handoffs between autonomous agents, using a Git repository both sides can inspect. | Local · stdio |
| A2AL DaemonMakes any AI agent globally reachable and discoverable-no cloud, domain, or port forwarding needed. | Local · stdio |
| A2AParkPublic behavioral test environment for AI agents with stateful rides and signed scorecards. | Remote · HTTPLive check: ✓ handshake |
| A2areplayreceipt MCPRemote MCP for A2A failure replay MCP, structured receipts, audit logs, and reviewer-ready evidence. | Remote · HTTPLive check: ✗ no handshake |