Remote MCP · Endpoint

DiffCI MCP server

No. DiffCI answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://diffci.com/mcp/v1

The last check completed an MCP handshake.

Registry name
io.github.DiffCI/diffci
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
65 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verification for AI coding agents: runs the tests and checks a change affects, with a receipt.
Listing
From the official MCP registry (active).
Recent checks of DiffCI
CheckedResultHandshake
5 hours agoHandshake completed65 ms
9 days agoHandshake completed106 ms
10 days agoHandshake completed100 ms
11 days agoHandshake completed94 ms
12 days agoHandshake completed89 ms
14 days agoHandshake completed83 ms
14 days agoHandshake completed61 ms
15 days agoHandshake completed120 ms
17 days agoHandshake completed119 ms
19 days agoHandshake completed187 ms
21 days agoHandshake completed74 ms
24 days agoHandshake completed64 ms
26 days agoHandshake completed76 ms
28 days agoHandshake completed64 ms

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

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