Remote MCP · Endpoint

DiffiCat MCP server

No. DiffiCat answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.difficat.com/mcp

The last check completed an MCP handshake.

Registry name
com.difficat/difficat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
164 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Compare a website before and after a migration: missing pages, content changes, visual diffs.
Listing
From the official MCP registry (active).
Recent checks of DiffiCat
CheckedResultHandshake
1 hour agoHandshake completed164 ms
2 days agoHandshake completed135 ms
4 days agoHandshake completed142 ms
6 days agoHandshake completed162 ms
7 days agoHandshake completed154 ms
9 days agoHandshake completed199 ms
10 days agoHandshake completed134 ms
11 days agoHandshake completed130 ms
14 days agoHandshake completed124 ms
15 days agoHandshake completed124 ms
17 days agoHandshake completed134 ms
18 days agoHandshake completed125 ms
20 days agoHandshake completed123 ms
21 days agoHandshake completed123 ms
22 days agoHandshake completed128 ms

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

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