Taproot MCP Server

by taproothq Your server? Claim it

answering

Taproot is answering right now. Last checked 1 min ago.

Persistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients.

Uptime history 47 days of history · worst day 98%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

388 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add taproot --transport http https://connect.taproothq.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "taproot": {
      "url": "https://connect.taproothq.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.taproot]
url = "https://connect.taproothq.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "taproot": {
      "url": "https://connect.taproothq.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "taproot": {
      "url": "https://connect.taproothq.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://connect.taproothq.com/mcp	streamable-http	needs key	366 ms	1 min ago

Alternatives to Taproot

same job, measured the same way

Mifactory Agent Memory

by mifactory-bot

Persistent memory for AI agents across Claude, ChatGPT and any MCP client.

2 tools answering

Butlerbrain

by butlerbrain

Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.

answering

WorkingMemory

by workingmemory

Persistent personal memory for AI assistants — save, search, and recall across every MCP client.

4 tools answering

Heirmos

by heirmos

Persistent memory shared across Claude, ChatGPT, Grok and other MCP clients.

answering

Jade Note

by jadenote

MCP-native notes and memory for ChatGPT, Claude, and other AI tools.

answering

Tabula

by nikhilbhima

Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.

answering

Memoir

by camgitt

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

226 installs/wk local only

Goldhold

by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

30 installs/wk answering

Taproot — questions

Answers built from our own checks of this server.

Why is there no tool list for Taproot?

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 Taproot 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 388 ms. The bar chart above shows every period we have measured.

How do I connect Taproot?

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 will need your own key: it refuses anonymous clients.

Does Taproot need an API key?

Yes. Every time we knock, Taproot answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Taproot?

It answers our handshake in 388 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.