Remote MCP · Endpoint

outcometick MCP server

No. outcometick answered an MCP handshake 21 minutes ago.

UpLast checked 21 minutes ago

Server URL

https://outcometick.com/v1/mcp/public

The last check completed an MCP handshake.

Registry name
io.github.outcometick/outcometick
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
301 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Listing
From the official MCP registry (active).
Recent checks of outcometick
CheckedResultHandshake
21 minutes agoHandshake completed301 ms
9 days agoHandshake completed197 ms
9 days agoHandshake completed243 ms
11 days agoHandshake completed202 ms
12 days agoHandshake completed250 ms
13 days agoHandshake completed202 ms
14 days agoHandshake completed189 ms
15 days agoHandshake completed199 ms
16 days agoHandshake completed194 ms
19 days agoHandshake completed198 ms
21 days agoHandshake completed258 ms
24 days agoHandshake completed210 ms
26 days agoHandshake completed191 ms
28 days agoHandshake completed206 ms

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