Remote MCP · Endpoint

com.skipseek/skipseek MCP server

No. com.skipseek/skipseek answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://skipseek.com/mcp

The last check completed an MCP handshake.

Registry name
com.skipseek/skipseek
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
189 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Polymarket, Manifold, Metaculus compared: one fair probability per question. No API key needed.
Website
https://skipseek.com/
Listing
From the official MCP registry (active).
Recent checks of com.skipseek/skipseek
CheckedResultHandshake
1 hour agoHandshake completed189 ms
2 days agoHandshake completed542 ms
4 days agoHandshake completed134 ms
5 days agoHandshake completed809 ms
7 days agoHandshake completed220 ms
8 days agoHandshake completed784 ms
9 days agoHandshake completed662 ms
12 days agoHandshake completed143 ms
13 days agoHandshake completed168 ms
15 days agoHandshake completed188 ms
16 days agoHandshake completed872 ms
17 days agoHandshake completed601 ms
19 days agoHandshake completed80 ms
20 days agoHandshake completed614 ms
20 days agoHandshake completed186 ms
21 days agoHandshake completed730 ms
22 days agoHandshake completed815 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.skipseek/skipseek and makes no claim about it beyond what these checks measured.