mcpbeat Sign in

Octopus.do MCP Server

answering

Octopus.do is answering right now. Last checked 6 min ago.

Read and edit octopus.do visual sitemaps: pages, blocks and review notes, as the signed-in user.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
242 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Octopus.do every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add sitemaps --transport http https://mcp.octopus.do/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sitemaps": {
      "url": "https://mcp.octopus.do/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sitemaps]
url = "https://mcp.octopus.do/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sitemaps": {
      "url": "https://mcp.octopus.do/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sitemaps": {
      "url": "https://mcp.octopus.do/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.octopus.do/mcp streamable-http sign-in 224 ms 6 min ago

Alternatives to Octopus.do

same job, measured the same way
xTiles
by xtiles

Read and structure notes, projects, tasks, and pages in the xTiles visual workspace.

answering
Autorenew Signup Lint
by jmshinhwa

Sixteen statutory checks on the signup page AB 2863 rewrote, in your editor and in the browser

269 installs/wk local only
PowerScroll
by cynacons

Read and edit a live local-first PowerScroll visual notebook.

43 installs/wk local only
C
The MCP Census
by mcpcensus

Vet any MCP server before you depend on it. Stamp: PASS, REVIEW, or BLOCK.

15 tools answering
AgentTakt
by ryoohshima

Review, edit, and approve AI agent task plans in a ComfyUI-style visual node editor in your terminal

227 installs/wk local only
Better Bear
by mreider

MCP server for Bear notes — read, search, create, edit, tag, and manage notes via CloudKit

127 installs/wk local only
Wiki.js
by ni-c

Search, read and edit Wiki.js pages, and manage its assets, users, groups and comments

73 installs/wk local only
Better Bear
by kuvopllc

MCP server for Bear notes — read, search, create, edit, tag, and manage notes via CloudKit

local only

Octopus.do — questions

Answers built from our own checks of this server.

Why is there no tool list for Octopus.do?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Octopus.do working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 242 ms. The bar chart above shows every period we have measured.
How do I connect Octopus.do?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Octopus.do?
No API key is involved. Octopus.do answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Octopus.do?
It answers our handshake in 242 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.