Remote MCP · Endpoint
net.sprtx/sprtx-mcp MCP server
No. net.sprtx/sprtx-mcp answered an MCP handshake 2 hours ago.
UpLast checked 2 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
- 402 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 18 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).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 402 ms |
| 1 day ago | Handshake completed | 272 ms |
| 3 days ago | Handshake completed | 249 ms |
| 3 days ago | Handshake completed | 152 ms |
| 4 days ago | Handshake completed | 159 ms |
| 5 days ago | Handshake completed | 374 ms |
| 7 days ago | Handshake completed | 269 ms |
| 10 days ago | Handshake completed | 141 ms |
| 12 days ago | Handshake completed | 280 ms |
| 15 days ago | Handshake completed | 337 ms |
| 17 days ago | Handshake completed | 438 ms |
| 19 days ago | Handshake completed | 271 ms |
| 21 days ago | Handshake completed | 271 ms |
| 23 days ago | Handshake completed | 707 ms |
| 25 days ago | Handshake completed | 768 ms |
| 26 days ago | Handshake completed | 148 ms |
| 28 days ago | Handshake completed | 203 ms |
| 29 days ago | Handshake completed | 145 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 net.sprtx/sprtx-mcp and makes no claim about it beyond what these checks measured.