Remote MCP · Endpoint

net.sprtx/sprtx-mcp MCP server

No. net.sprtx/sprtx-mcp answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.sprtx.net/

The last check completed an MCP handshake.

Registry name
net.sprtx/sprtx-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
271 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent-native sports token network. 1,435 tokens across 98 sports, 9 global regions.
Repository
https://github.com/sprtxbabe/sprtx-mcp
Listing
From the official MCP registry (active).
Recent checks of net.sprtx/sprtx-mcp
CheckedResultHandshake
5 hours agoHandshake completed271 ms
2 days agoHandshake completed707 ms
4 days agoHandshake completed768 ms
5 days agoHandshake completed148 ms
7 days agoHandshake completed203 ms
8 days agoHandshake completed145 ms
9 days agoHandshake completed515 ms
12 days agoHandshake completed244 ms
13 days agoHandshake completed256 ms
15 days agoHandshake completed284 ms
16 days agoHandshake completed571 ms
17 days agoHandshake completed257 ms
18 days agoHandshake completed242 ms
19 days agoHandshake completed505 ms
20 days agoHandshake completed247 ms
21 days agoHandshake completed410 ms
22 days agoHandshake completed249 ms

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

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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