Remote MCP · Endpoint

Stackfacts MCP server

No. Stackfacts answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://stackfacts.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
app.vercel.stackfacts/stackfacts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
105 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Neutral, sourced, dated facts for choosing software: price, free tier, idle rules, security record.
Listing
From the official MCP registry (deprecated).
Recent checks of Stackfacts
CheckedResultHandshake
4 hours agoHandshake completed105 ms
2 days agoHandshake completed86 ms
5 days agoHandshake completed86 ms
7 days agoHandshake completed96 ms
9 days agoHandshake completed533 ms
11 days agoHandshake completed86 ms
13 days agoHandshake completed216 ms
15 days agoHandshake completed108 ms
17 days agoHandshake completed92 ms
18 days agoHandshake completed99 ms
20 days agoHandshake completed101 ms
21 days agoHandshake completed79 ms
23 days agoHandshake completed166 ms

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

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