Remote MCP · Endpoint
a2a2p — Agent-to-Agent-to-Physical MCP server
No. a2a2p — Agent-to-Agent-to-Physical answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://a2a2p.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.a2a2p/a2a2p
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 227 ms
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Turn agent intent into physical parts: engineering review, measured geometry, calibrated pricing.
- Website
- https://a2a2p.com/
- Repository
- https://github.com/Deadlypillow/a2a2p
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 227 ms |
| 1 day ago | Handshake completed | 241 ms |
| 2 days ago | Handshake completed | 54 ms |
| 3 days ago | Handshake completed | 202 ms |
| 4 days ago | Handshake completed | 259 ms |
| 5 days ago | Handshake completed | 510 ms |
| 7 days ago | Handshake completed | 630 ms |
| 10 days ago | Handshake completed | 118 ms |
| 12 days ago | Handshake completed | 425 ms |
| 14 days ago | Handshake completed | 163 ms |
| 17 days ago | Handshake completed | 153 ms |
| 19 days ago | Handshake completed | 109 ms |
| 21 days ago | Handshake completed | 138 ms |
| 23 days ago | Handshake completed | 127 ms |
| 25 days ago | Handshake completed | 97 ms |
| 26 days ago | Handshake completed | 95 ms |
| 28 days ago | Handshake completed | 214 ms |
| 29 days ago | Handshake completed | 344 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with a2a2p — Agent-to-Agent-to-Physical and makes no claim about it beyond what these checks measured.