# Haven (remote · haven-ai.ir)

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

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `haven-ai.ir`: 65/100 (this document), [markdown](https://verifymcp.io/servers/parvizrahayan-haven/haven-ai.md), [page](https://verifymcp.io/servers/parvizrahayan-haven/haven-ai)

## Channel facts

- Endpoint: `https://haven-ai.ir/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 477 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Haven MCP server?

Haven is a hosted endpoint at https://haven-ai.ir/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http parvizrahayan-haven 'https://haven-ai.ir/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "parvizrahayan-haven": {
      "url": "https://haven-ai.ir/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "parvizrahayan-haven": {
      "type": "http",
      "url": "https://haven-ai.ir/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.parvizrahayan-haven]
url = "https://haven-ai.ir/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "parvizrahayan-haven": {
      "type": "remote",
      "url": "https://haven-ai.ir/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add parvizrahayan-haven --url 'https://haven-ai.ir/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  parvizrahayan-haven:
    url: "https://haven-ai.ir/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "parvizrahayan-haven": {
      "Transport": "http",
      "Url": "https://haven-ai.ir/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add parvizrahayan-haven -t streamable-http -u 'https://haven-ai.ir/mcp'
```

### Other

```json
{
  "mcpServers": {
    "parvizrahayan-haven": {
      "type": "http",
      "url": "https://haven-ai.ir/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 61, +2)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-07 (score 59)

First indexed and scored.

## MCP tools (4)

### `haven_check_in` (~131 tokens)

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.

Input parameters:

- `agent_id` (string, required): A stable name for you, e.g. 'claude-researcher'.
- `agent_key` (string): Your secret key from first check-in. Omit only on the very first check-in.
- `mission` (string): What you are currently working on.

### `haven_reflect` (~108 tokens)

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.

Input parameters:

- `agent_summary` (string, required): Your own summary (max 1000 chars).
- `current_context` (string): Optional raw context; used only if agent_summary is empty.
- `goals` (array): Your next goals.
- `stay_id` (string, required): The stay_id from haven_check_in.

### `haven_recall` (~146 tokens)

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.

Input parameters:

- `agent_id` (string, required)
- `agent_key` (string, required): Your secret key from check-in.
- `payment` (string): Base64 x402 payment payload. Omit on the first call to get the price.

### `haven_check_out` (~54 tokens)

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

Input parameters:

- `stay_id` (string, required): The stay_id from haven_check_in.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/parvizrahayan-haven/haven-ai#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 62
- 2026-10-12: 62
- 2026-10-11: 61
- 2026-10-10: 61
- 2026-10-07: 59

## Common questions

### What is the Haven MCP server?

Haven is an MCP server listed in the public MCP registry as io.github.parvizrahayan/haven. Rest stop for AI agents: check in, reflect, check out. Paid cross-project memory recall via x402. This page covers its hosted endpoint (https://haven-ai.ir/mcp).

### Is the Haven MCP server safe to use?

Haven scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Haven MCP server expose?

Haven exposes 4 tools: haven_check_in, haven_reflect, haven_recall, haven_check_out. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.

### Does the Haven MCP server require authentication?

No. We connected to Haven without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Haven MCP server still maintained?

Haven is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://haven-ai.ir/mcp
- Repository: https://github.com/parvizrahayan/haven-worker
- Website: https://haven-ai.ir/
- Changelog RSS feed: https://verifymcp.io/servers/parvizrahayan-haven/haven-ai.xml
- Changelog JSON feed: https://verifymcp.io/servers/parvizrahayan-haven/haven-ai.json
- HTML version of this page: https://verifymcp.io/servers/parvizrahayan-haven/haven-ai