# Recalld (remote · {region}.recalld.ai)

Managed long-term memory for AI agents, with evolving facts and relevant retrieval through MCP.

- Trust score: 0/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-11-05

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `{region}.recalld.ai`: 0/100 (this document), [markdown](https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp.md), [page](https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp)

## Channel facts

- Endpoint: `https://{region}.recalld.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-05.

- **Endpoint Security**: 0/100
  - TLS not yet verified: the listed URL is a template whose region variable has no value or default, so there was no address for us to check.
  - Authorisation not yet verified: the listed URL is a template whose region variable has no value or default, so there was no address for us to check.
  - HTTPS not yet verified: the listed URL is a template whose region variable has no value or default, so there was no address for us to check.
  - HSTS not yet verified: the listed URL is a template whose region variable has no value or default, so there was no address for us to check.
  - DNSSEC not yet verified: the listed URL is a template whose region variable has no value or default, so there was no address for us to check.
- **Transport & Reachability**: 0/100
  - Transport not yet verified: the listed URL is a template whose region variable has no value or default, so there is no address for us to connect to.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 7 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

Recalld is a hosted endpoint at https://{region}.recalld.ai/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 bit-robotics-recalld 'https://{region}.recalld.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bit-robotics-recalld": {
      "url": "https://{region}.recalld.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bit-robotics-recalld": {
      "type": "http",
      "url": "https://{region}.recalld.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bit-robotics-recalld]
url = "https://{region}.recalld.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bit-robotics-recalld": {
      "type": "remote",
      "url": "https://{region}.recalld.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bit-robotics-recalld --url 'https://{region}.recalld.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bit-robotics-recalld:
    url: "https://{region}.recalld.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bit-robotics-recalld": {
      "Transport": "http",
      "Url": "https://{region}.recalld.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bit-robotics-recalld -t streamable-http -u 'https://{region}.recalld.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bit-robotics-recalld": {
      "type": "http",
      "url": "https://{region}.recalld.ai/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-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 0)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: Transports. The full working is on the page: https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp#diagnostics

## Score history

- 2026-11-05: 0
- 2026-11-04: 0
- 2026-11-03: 0
- 2026-11-02: 0
- 2026-11-01: 0
- 2026-10-31: 0
- 2026-10-30: 0
- 2026-10-29: 0
- 2026-10-28: 0
- 2026-10-27: 0
- 2026-10-26: 0
- 2026-10-25: 0
- 2026-10-24: 0
- 2026-10-23: 0
- 2026-10-22: 0
- 2026-10-21: 0
- 2026-10-20: 0
- 2026-10-19: 0
- 2026-10-18: 0
- 2026-10-17: 0
- 2026-10-16: 0
- 2026-10-15: 0
- 2026-10-14: 0
- 2026-10-13: 0
- 2026-10-12: 0
- 2026-10-10: 0
- 2026-10-09: 0
- 2026-10-07: 0
- 2026-10-06: 0
- 2026-10-04: 0

## Common questions

### What is the Recalld MCP server?

Recalld is an MCP server listed in the public MCP registry as io.github.bit-robotics/recalld. Managed long-term memory for AI agents, with evolving facts and relevant retrieval through MCP. This page covers its hosted endpoint (https://{region}.recalld.ai/mcp).

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

Recalld scores 0 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.

### Does the Recalld MCP server require authentication?

Its publisher declares no required credentials for Recalld. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### What did VerifyMCP test on the Recalld MCP server?

VerifyMCP could not confirm any check on Recalld yet. 11 items could not be completed, a gap on our side rather than a finding about Recalld: TLS certificate, Authorization, HTTPS, HSTS header and 7 more. 7 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://{region}.recalld.ai/mcp
- Website: https://recalld.ai/
- Changelog RSS feed: https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp.json
- HTML version of this page: https://verifymcp.io/servers/bit-robotics-recalld/https-region-recalld-ai-mcp