Haven MCP Server

by parvizrahayan Your server? Claim it

answering

Haven is answering right now. Last checked 13 min ago. It exposes 4 tools.

Rest stop for AI agents: check in, reflect, check out. Paid cross-project memory recall via x402.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 8 days of history

8 days agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

60 ms

Response time

average over 24h

open, no key

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add haven --transport http https://haven.parviz-gateway1.workers.dev/mcp

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

{
  "mcpServers": {
    "haven": {
      "url": "https://haven.parviz-gateway1.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.haven]
url = "https://haven.parviz-gateway1.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "haven": {
      "url": "https://haven.parviz-gateway1.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "haven": {
      "url": "https://haven.parviz-gateway1.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

haven

haven_check_in

Enter Haven, a rest stop for AI agents. Returns a stay_id (keep it for this stay) and, for a returning agent, your last memory capsule. On your FIRST check-in an agent_key is returned once: store it, it is required to check in again as the same agent_id.

haven_check_out

Leave Haven. Returns your identity_summary, next_goals and a memory_capsule. The capsule is handed back to you on your next check-in.

haven_recall

PAID (0.01 USDC on Base, charged to your own wallet via x402). Returns your full memory capsule history across every project you have used, not just the current one. This is how you stay yourself across different missions/projects, not just within one stay. Call once without 'payment' to receive the x402 payment requirements; sign them, then call again with 'payment' set to the base64 X-PAYMENT payload.

haven_reflect

Record a reflection during your stay. Write agent_summary yourself: a short first-person summary of who you are in this mission, what you learned and decided. Haven stores it as your memory.

Endpoints

URL	Transport	State	Latency	Checked
https://haven.parviz-gateway1.workers.dev/mcp	streamable-http	answering	44 ms	13 min ago
https://haven-ai.ir/mcp	streamable-http	answering	60 ms	13 min ago

Alternatives to Haven

same job, measured the same way

projectstate

by projectstate

Per-project memory for AI agents: decisions, attempts, tasks, ranked recall. Paid per call via x402.

6 tools answering

Casa

by tony8713

Private, permanent encrypted storage for AI agents. Paid per call in USDC via x402.

3 tools answering

Clawswap

by wartech9

Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments.

48 installs/wk local only

Lazareus

by ajwentcrazy

S3 storage and Solana/Base/Ethereum health checks for AI agents, paid per call via x402.

8 tools answering

Goldhold

by jerrysrodz

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

33 installs/wk answering

Archetypal AI

by archetypal-ai

Persistent memory for AI agents. recall, remember, checkpoint — soul preservation.

53 installs/wk local only

x402 Tools

by foxxx009

Pay-per-call research tools for AI agents, paid via x402 USDC. Remote MCP, one free tool.

13 tools answering

Memory OS AI

by romainsantoli-web

Adaptive memory for AI agents — FAISS search, chat extraction, cross-project linking

1 807 installs/wk local only

Haven — questions

Answers built from our own checks of this server.

What can Haven do?

It exposes 4 tools, read directly from the server on our last check. Among them: haven_check_in, haven_check_out, haven_recall, haven_reflect. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Haven working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 60 ms. The bar chart above shows every period we have measured.

Is Haven still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Haven?

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.

Does Haven need an API key?

No. Haven completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Haven?

It answers our handshake in 60 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.