Remote MCP · Endpoint

Kineticist MCP server

No. Kineticist answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://www.kineticist.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.kineticist/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
99 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pinball news, games and editions, designers, places to play and the Hype Index from Kineticist.
Listing
From the official MCP registry (active).
Recent checks of Kineticist
CheckedResultHandshake
4 days agoHandshake completed99 ms
4 days agoHandshake completed149 ms
5 days agoHandshake completed82 ms
6 days agoHandshake completed532 ms
8 days agoHandshake completed114 ms
8 days agoHandshake completed110 ms
9 days agoHandshake completed303 ms
10 days agoHandshake completed104 ms
12 days agoHandshake completed124 ms
15 days agoHandshake completed85 ms
17 days agoHandshake completed131 ms
20 days agoHandshake completed67 ms
22 days agoHandshake completed84 ms
24 days agoHandshake completed70 ms

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