Remote MCP · Endpoint

team.jogo/mcp MCP server

No. team.jogo/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://jogo.team/mcp

The last check completed an MCP handshake.

Registry name
team.jogo/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Find pickup soccer or drop-in football games via your AI. 70+ cities, one-click RSVP.
Listing
From the official MCP registry (active).
Recent checks of team.jogo/mcp
CheckedResultHandshake
1 hour agoHandshake completed121 ms
2 days agoHandshake completed205 ms
4 days agoHandshake completed118 ms
6 days agoHandshake completed127 ms
7 days agoHandshake completed125 ms
8 days agoHandshake completed221 ms
9 days agoHandshake completed189 ms
12 days agoHandshake completed98 ms
13 days agoHandshake completed129 ms
15 days agoHandshake completed115 ms
17 days agoHandshake completed137 ms
18 days agoHandshake completed112 ms
19 days agoHandshake completed122 ms
20 days agoHandshake completed184 ms
21 days agoHandshake completed99 ms
21 days agoHandshake completed175 ms
23 days agoHandshake completed65 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.

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