mcpbeat Sign in

innernet MCP Server

answering

innernet is answering right now. Last checked 6 min ago.

Your versioned memory across every AI tool — context maps, personal memory, and tasks over MCP.

Uptime history 48 days of history · worst day 0%
48 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
658 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check innernet 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 innernet --transport http https://innernet.live/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "innernet": {
      "url": "https://innernet.live/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.innernet]
url = "https://innernet.live/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "innernet": {
      "url": "https://innernet.live/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "innernet": {
      "url": "https://innernet.live/api/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://innernet.live/api/mcp streamable-http sign-in 688 ms 6 min ago

Alternatives to innernet

same job, measured the same way
Atlaso
by atlaso

AI memory layer — one shared, persistent memory across every AI tool you connect.

answering
Nexus Catalyst
by nexus-catalyst

Cross-tool persistent memory and context for AI assistants over MCP.

answering
Connect
by odei

Governed personal world model and memory for your AI agent. Pair once, connect over MCP.

7 tools answering
Cachetank MCP
by jacobsilver7-art

CacheTank MCP server gives every AI tool your personal context so you never start from zero.

31 installs/wk local only
MCP Memento
by annibale-x

An MCP server that provides persistent memory and context management across sessions

197 installs/wk local only
memsprout
by memsprout

shared AI-context layer for teams — persistent memory your agents search and update over MCP

answering
Memoir
by camgitt

Persistent memory for AI coding tools via MCP. Remembers across sessions and machines.

226 installs/wk local only
Memoro
by circassian1977-byte

Personal AI memory layer on your own computer. Read/write durable memory across MCP clients.

62 installs/wk local only

innernet — questions

Answers built from our own checks of this server.

Why is there no tool list for innernet?
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 innernet 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 658 ms. The bar chart above shows every period we have measured.
How do I connect innernet?
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 innernet?
No API key is involved. innernet 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 innernet?
It answers our handshake in 658 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.