Remote MCP · Endpoint

ourpr. MCP server

No. ourpr. answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ourpr.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.joeyaflores/ourpr-courses
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Measured race courses, open to all, and your own runs, Blocks and plans once you sign in.
Listing
From the official MCP registry (active).
Recent checks of ourpr.
CheckedResultHandshake
1 hour agoHandshake completed294 ms
9 days agoHandshake completed192 ms
10 days agoHandshake completed249 ms
11 days agoHandshake completed209 ms
12 days agoHandshake completed662 ms
14 days agoHandshake completed216 ms
14 days agoHandshake completed198 ms
15 days agoHandshake completed298 ms
17 days agoHandshake completed258 ms
19 days agoHandshake completed179 ms
21 days agoHandshake completed546 ms
24 days agoHandshake completed768 ms
26 days agoHandshake completed313 ms
28 days agoHandshake completed179 ms

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

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