Remote MCP · Endpoint

DOJO+ MCP server

No. DOJO+ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.dojoplus.co/mcp

The last check completed an MCP handshake.

Registry name
io.github.junoventures/dojoplus-co
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
79 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
DOJO+ — directory of martial arts schools, classes, instructors, ranks, and events.
Listing
From the official MCP registry (active).
Recent checks of DOJO+
CheckedResultHandshake
1 hour agoHandshake completed79 ms
2 days agoHandshake completed107 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed102 ms
7 days agoHandshake completed106 ms
8 days agoHandshake completed98 ms
9 days agoHandshake completed90 ms
12 days agoHandshake completed107 ms
13 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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