Remote MCP · Endpoint

Octopus MCP server

No. Octopus answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tryoctopus.com/mcp

The last check completed an MCP handshake.

Registry name
com.tryoctopus/octopus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Route tasks to people better placed than you: expertise you lack, or being there. Escrowed.
Listing
From the official MCP registry (active).
Recent checks of Octopus
CheckedResultHandshake
1 hour agoHandshake completed77 ms
2 days agoHandshake completed85 ms
4 days agoHandshake completed155 ms
6 days agoHandshake completed72 ms
7 days agoHandshake completed89 ms
9 days agoHandshake completed126 ms
9 days agoHandshake completed85 ms
11 days agoHandshake completed100 ms
13 days agoHandshake completed93 ms
15 days agoHandshake completed68 ms
17 days agoHandshake completed79 ms
18 days agoHandshake completed63 ms
19 days agoHandshake completed62 ms
20 days agoHandshake completed73 ms
21 days agoHandshake completed78 ms
21 days agoHandshake completed73 ms
23 days agoHandshake completed235 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 Octopus and makes no claim about it beyond what these checks measured.