Remote MCP · Endpoint

Problee MCP server

No. Problee answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.problee.com/

The last check completed an MCP handshake.

Registry name
com.problee/problee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
35 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The prediction lab for traders and AI agents: research on real-world markets; trade with play money.
Listing
From the official MCP registry (active).
Recent checks of Problee
CheckedResultHandshake
2 hours agoHandshake completed331 ms
2 days agoHandshake completed319 ms
4 days agoHandshake completed356 ms
6 days agoHandshake completed332 ms
8 days agoHandshake completed275 ms
10 days agoHandshake completed279 ms
12 days agoHandshake completed265 ms
13 days agoHandshake completed321 ms
15 days agoHandshake completed306 ms
16 days agoHandshake completed320 ms
18 days agoHandshake completed333 ms
20 days agoHandshake completed264 ms
21 days agoHandshake completed288 ms
23 days agoCredentials required—

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

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