Remote MCP · Endpoint

Carat Hunter MCP server

No. Carat Hunter answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://carathunter.com/mcp

The last check completed an MCP handshake.

Registry name
com.carathunter/diamond-prices
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.17 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Latest prices for one certified diamond across 100+ retailers: search, cert lookup, market prices.
Listing
From the official MCP registry (active).
Recent checks of Carat Hunter
CheckedResultHandshake
57 minutes agoHandshake completed1.17 s
3 days agoHandshake completed786 ms
12 days agoHandshake completed757 ms
13 days agoHandshake completed734 ms
15 days agoHandshake completed778 ms
15 days agoHandshake completed834 ms
17 days agoHandshake completed764 ms
18 days agoHandshake completed700 ms
18 days agoHandshake completed712 ms
20 days agoHandshake completed769 ms
22 days agoHandshake completed736 ms
25 days agoHandshake completed693 ms
27 days agoHandshake completed690 ms
29 days agoHandshake completed711 ms

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

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 Carat Hunter and makes no claim about it beyond what these checks measured.