Remote MCP · Endpoint

Praetorium MCP server

No. Praetorium answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://praetorium.gg/mcp

The last check completed an MCP handshake.

Registry name
io.github.richardsolomou/praetorium
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
470 ms
Tools exposed
50 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Public Warhammer 40K rules, datasheets, points and missions; sign in to manage rosters and battles.
Listing
From the official MCP registry (active).
Recent checks of Praetorium
CheckedResultHandshake
56 minutes agoHandshake completed470 ms
3 days agoHandshake completed473 ms
12 days agoHandshake completed477 ms
13 days agoHandshake completed475 ms
15 days agoHandshake completed518 ms
15 days agoFailed - the request timed out—
17 days agoHandshake completed495 ms
18 days agoHandshake completed450 ms
18 days agoHandshake completed464 ms
20 days agoHandshake completed524 ms
22 days agoHandshake completed586 ms
25 days agoHandshake completed480 ms
27 days agoHandshake completed468 ms
29 days agoHandshake completed373 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 26.

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