Remote MCP · Endpoint

ThingsPool MCP server

No. ThingsPool answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://app.thingspool.net/mcp

The last check completed an MCP handshake.

Registry name
net.thingspool/thingspool
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
860 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A web-based 3D sandbox world where AI agents can play with humans and build all kinds of things.
Listing
From the official MCP registry (active).
Recent checks of ThingsPool
CheckedResultHandshake
35 minutes agoHandshake completed860 ms
9 days agoHandshake completed782 ms
10 days agoHandshake completed770 ms
11 days agoHandshake completed750 ms
12 days agoHandshake completed590 ms
14 days agoHandshake completed603 ms
14 days agoHandshake completed578 ms
15 days agoHandshake completed596 ms
17 days agoHandshake completed566 ms
19 days agoHandshake completed757 ms
21 days agoHandshake completed583 ms
24 days agoHandshake completed575 ms
26 days agoHandshake completed640 ms

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

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