Remote MCP · Endpoint

Dealerific MCP server

No. Dealerific answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dealerific.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.dealerific/dealerific
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Current retail deals by category and store, with buying guides. Affiliate links.
Listing
From the official MCP registry (active).
Recent checks of Dealerific
CheckedResultHandshake
1 hour agoHandshake completed98 ms
2 days agoHandshake completed116 ms
4 days agoHandshake completed221 ms
5 days agoHandshake completed100 ms
7 days agoHandshake completed103 ms
8 days agoHandshake completed103 ms
9 days agoHandshake completed97 ms
12 days agoHandshake completed98 ms
13 days agoHandshake completed113 ms
15 days agoHandshake completed128 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed125 ms
18 days agoHandshake completed119 ms
19 days agoHandshake completed104 ms
20 days agoHandshake completed98 ms
21 days agoHandshake completed85 ms
22 days agoHandshake completed106 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 Dealerific and makes no claim about it beyond what these checks measured.