Remote MCP · Endpoint

Clairvoyance MCP server

No. Clairvoyance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://clairvoyance.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.clairvoyance/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
256 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Software design skills for AI coding agents, inspired by A Philosophy of Software Design.
Listing
From the official MCP registry (active).
Recent checks of Clairvoyance
CheckedResultHandshake
1 hour agoHandshake completed256 ms
20 hours agoHandshake completed77 ms
1 day agoHandshake completed108 ms
2 days agoHandshake completed147 ms
4 days agoHandshake completed550 ms
7 days agoHandshake completed127 ms
9 days agoHandshake completed142 ms
12 days agoHandshake completed82 ms
14 days agoHandshake completed77 ms
16 days agoHandshake completed121 ms
18 days agoHandshake completed104 ms
20 days agoHandshake completed167 ms
22 days agoHandshake completed115 ms
23 days agoHandshake completed126 ms
25 days agoHandshake completed170 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 Clairvoyance and makes no claim about it beyond what these checks measured.