Remote MCP · Endpoint

Folionomiq MCP server

No. Folionomiq answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://folionomiq.com/mcp

The last check completed an MCP handshake.

Registry name
com.folionomiq/folionomiq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
354 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Measures a portfolio from price history: real bets, look-through, past crises in money. No advice.
Listing
From the official MCP registry (active).
Recent checks of Folionomiq
CheckedResultHandshake
1 hour agoHandshake completed354 ms
1 day agoHandshake completed287 ms
4 days agoHandshake completed427 ms
6 days agoHandshake completed186 ms
7 days agoHandshake completed331 ms
9 days agoHandshake completed173 ms
10 days agoHandshake completed751 ms
11 days agoHandshake completed304 ms
14 days agoHandshake completed321 ms
15 days agoHandshake completed325 ms
17 days agoHandshake completed271 ms
18 days agoHandshake completed259 ms
20 days agoHandshake completed322 ms
21 days agoHandshake completed136 ms
22 days agoHandshake completed304 ms
22 days agoHandshake completed291 ms

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

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