Remote MCP · Endpoint
com.x402supply/entity-resolve MCP server
No. com.x402supply/entity-resolve answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://entity-resolve.x402supply.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.x402supply/entity-resolve
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 61 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Fuzzy entity resolution and dedupe for names, addresses, and company records. $0.02/call via x402.
- Website
- https://x402supply.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 61 ms |
| 1 day ago | Handshake completed | 214 ms |
| 2 days ago | Handshake completed | 672 ms |
| 3 days ago | Handshake completed | 256 ms |
| 4 days ago | Handshake completed | 148 ms |
| 5 days ago | Handshake completed | 158 ms |
| 6 days ago | Handshake completed | 126 ms |
| 9 days ago | Handshake completed | 164 ms |
| 12 days ago | Handshake completed | 124 ms |
| 14 days ago | Handshake completed | 171 ms |
| 16 days ago | Handshake completed | 158 ms |
| 18 days ago | Handshake completed | 153 ms |
| 20 days ago | Handshake completed | 143 ms |
| 22 days ago | Handshake completed | 173 ms |
| 24 days ago | Handshake completed | 105 ms |
| 26 days ago | Handshake completed | 79 ms |
| 27 days ago | Handshake completed | 124 ms |
| 28 days ago | Handshake completed | 376 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 com.x402supply/entity-resolve and makes no claim about it beyond what these checks measured.