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
143 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Fuzzy entity resolution and dedupe for names, addresses, and company records. $0.02/call via x402.
Listing
From the official MCP registry (active).
Recent checks of com.x402supply/entity-resolve
CheckedResultHandshake
1 hour agoHandshake completed143 ms
2 days agoHandshake completed173 ms
4 days agoHandshake completed105 ms
5 days agoHandshake completed79 ms
7 days agoHandshake completed124 ms
8 days agoHandshake completed376 ms
9 days agoHandshake completed76 ms
12 days agoHandshake completed123 ms
13 days agoHandshake completed222 ms
15 days agoHandshake completed155 ms
16 days agoHandshake completed277 ms
18 days agoHandshake completed121 ms
19 days agoHandshake completed110 ms
20 days agoHandshake completed117 ms
20 days agoHandshake completed144 ms
21 days agoHandshake completed147 ms
22 days agoHandshake completed458 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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.