Remote MCP · Endpoint

Stackfacts MCP server

No. Stackfacts answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes 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
78 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 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
43 minutes agoHandshake completed78 ms
3 days agoHandshake completed61 ms
13 days agoHandshake completed75 ms
13 days agoHandshake completed639 ms
15 days agoHandshake completed555 ms
15 days agoHandshake completed72 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed109 ms
18 days agoHandshake completed124 ms
20 days agoHandshake completed91 ms
22 days agoHandshake completed105 ms
25 days agoHandshake completed86 ms
27 days agoHandshake completed86 ms
29 days agoHandshake completed96 ms

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

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.