Remote MCP · Endpoint

Genius MCP server

No. Genius answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://gateway.pipeworx.io/genius/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/genius
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
Not measured yet
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Genius MCP — wraps the Genius API (api.genius.com)
Listing
From the official MCP registry (active).
Recent checks of Genius
CheckedResultHandshake
40 minutes agoHandshake completed81 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed51 ms
5 days agoHandshake completed52 ms
7 days agoHandshake completed81 ms
8 days agoHandshake completed45 ms
9 days agoFailed - the request timed out—
12 days agoHandshake completed54 ms
14 days agoHandshake completed54 ms
15 days agoHandshake completed39 ms
17 days agoHandshake completed42 ms
18 days agoHandshake completed40 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed98 ms
20 days agoHandshake completed40 ms
21 days agoHandshake completed35 ms
23 days agoHandshake completed61 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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.

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