# Brainiall Memory (remote · api.brainiall.com)

Persistent semantic memory storage, associative recall, and recent memory index by namespace.

- Trust score: 36/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `api.brainiall.com`: 36/100 (this document), [markdown](https://verifymcp.io/servers/com-brainiall-memory/mcp-memory-mcp.md), [page](https://verifymcp.io/servers/com-brainiall-memory/mcp-memory-mcp)

## Channel facts

- Endpoint: `https://api.brainiall.com/mcp/memory/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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **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 blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 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 Brainiall Memory MCP server?

Brainiall Memory is a hosted endpoint at https://api.brainiall.com/mcp/memory/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 com-brainiall-memory 'https://api.brainiall.com/mcp/memory/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-brainiall-memory": {
      "url": "https://api.brainiall.com/mcp/memory/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-brainiall-memory": {
      "type": "http",
      "url": "https://api.brainiall.com/mcp/memory/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-brainiall-memory]
url = "https://api.brainiall.com/mcp/memory/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-brainiall-memory": {
      "type": "remote",
      "url": "https://api.brainiall.com/mcp/memory/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-brainiall-memory --url 'https://api.brainiall.com/mcp/memory/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-brainiall-memory:
    url: "https://api.brainiall.com/mcp/memory/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-brainiall-memory": {
      "Transport": "http",
      "Url": "https://api.brainiall.com/mcp/memory/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-brainiall-memory -t streamable-http -u 'https://api.brainiall.com/mcp/memory/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-brainiall-memory": {
      "type": "http",
      "url": "https://api.brainiall.com/mcp/memory/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-18 (score 36, +7)

- [security regression] Endpoint reachability: unreachable → behind authorisation
- [security regression] Authorization: unverified → fail
- [security regression] Transport: fail → unverified
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-17 (score 29, −7)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-15 (score 36, 0)

- [security regression] Endpoint reachability: behind authorisation → unreachable
- [security regression] Transport: unverified → fail
- [security regression] Authorization: fail → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema.

### 2026-09-12 (score 36, +4)

- [security regression] Endpoint reachability: unreachable → behind authorisation
- [security regression] Authorization: unverified → fail
- [security regression] Transport: fail → unverified
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-11 (score 32, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-10 (score 48, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-09 (score 64, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-07 (score 80, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.37 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

## MCP tools (4)

### `remember` (~178 tokens)

Remember Fact

Store a durable fact, preference, or decision into persistent memory across sessions.

Use when you discover an important user preference, key background detail,
architecture choice, or durable fact that must be recalled in future sessions.
Do NOT use for storing entire conversation logs or transient temporary state.

Input parameters:

- `metadata`: Optional structured key-value metadata to attach to this memory (e.g., {'category': 'user_preference', 'source': 'onboarding'}).
- `namespace` (string, required): Isolated storage namespace for the agent or user (e.g., 'user_123_pref', 'agent_project_alpha'). Must be 1-64 alphanumeric characters, hyphens, underscores, or dots.
- `text` (string, required): Durable fact, preference, decision, or memory to store. Store key facts for future sessions; do NOT store raw full chat transcripts.

### `recall` (~126 tokens)

Recall Memories

Search persistent memory by semantic meaning to retrieve past facts, context, or preferences.

Use when answering queries that benefit from prior user context, past decisions,
or stored preferences. Performs vector search (semantic similarity) rather
than simple keyword match.

Input parameters:

- `limit` (integer): Maximum number of memory items to return (default: 5, ceiling: 50).
- `namespace` (string, required): Storage namespace to search (e.g., 'user_123_pref', 'agent_project_alpha').
- `query` (string, required): Search query describing the fact, context, or topic to find by semantic similarity.

### `recent_memories` (~101 tokens)

List Recent Memories

Retrieve the most recently recorded memories for a namespace to re-orient at session startup.

Use at the beginning of a conversation or task to discover recent context,
active objectives, or latest user facts recorded in this namespace.

Input parameters:

- `limit` (integer): Maximum number of recent memories to return (default: 5, ceiling: 50).
- `namespace` (string, required): Storage namespace to inspect (e.g., 'user_123_pref', 'agent_project_alpha').

### `check_memory_service` (~35 tokens)

Check Memory Service

Check health status and connectivity of the persistent memory backend service.

Returns:
    Dict with health status ('healthy' or error details).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-brainiall-memory/mcp-memory-mcp#diagnostics

## Score history

- 2026-09-21: 36
- 2026-09-20: 36
- 2026-09-19: 36
- 2026-09-18: 36
- 2026-09-17: 29
- 2026-09-16: 36
- 2026-09-15: 36
- 2026-09-14: 36
- 2026-09-13: 36
- 2026-09-12: 36
- 2026-09-11: 32
- 2026-09-10: 48
- 2026-09-09: 64
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 78
- 2026-08-30: 77
- 2026-08-29: 77
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75

## Common questions

### What is the Brainiall Memory MCP server?

Brainiall Memory is an MCP server listed in the public MCP registry as com.brainiall/memory. Persistent semantic memory storage, associative recall, and recent memory index by namespace. This page covers its hosted endpoint (https://api.brainiall.com/mcp/memory/mcp).

### Is the Brainiall Memory MCP server safe to use?

Brainiall Memory scores 36 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 Brainiall Memory MCP server expose?

Brainiall Memory exposes 4 tools: remember, recall, recent_memories, check_memory_service. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.

### Does the Brainiall Memory MCP server require authentication?

Yes. Brainiall Memory asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Brainiall Memory MCP server still maintained?

Brainiall Memory is still listed as active in the MCP registry. We last reached this channel on 21 September 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://api.brainiall.com/mcp/memory/mcp
- Website: https://brainiall.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-brainiall-memory/mcp-memory-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-brainiall-memory/mcp-memory-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-brainiall-memory/mcp-memory-mcp