# io.github.soluai-spa/solucortex-mcp (remote · mcp.solucortex.ai)

Living technical memory for AI agents: recall approved project context, record what was learned.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.solucortex.ai`: 80/100 (this document), [markdown](https://verifymcp.io/servers/soluai-spa-solucortex-mcp/mcp.md), [page](https://verifymcp.io/servers/soluai-spa-solucortex-mcp/mcp)
- pypi · `solucortex-mcp`: 66/100, [markdown](https://verifymcp.io/servers/soluai-spa-solucortex-mcp/solucortex-mcp.md), [page](https://verifymcp.io/servers/soluai-spa-solucortex-mcp/solucortex-mcp)

## Channel facts

- Endpoint: `https://mcp.solucortex.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.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-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1379 tokens (~229/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.soluai-spa/solucortex-mcp server?

io.github.soluai-spa/solucortex-mcp is a hosted endpoint at https://mcp.solucortex.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 soluai-spa-solucortex-mcp 'https://mcp.solucortex.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "soluai-spa-solucortex-mcp": {
      "url": "https://mcp.solucortex.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "soluai-spa-solucortex-mcp": {
      "type": "http",
      "url": "https://mcp.solucortex.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.soluai-spa-solucortex-mcp]
url = "https://mcp.solucortex.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "soluai-spa-solucortex-mcp": {
      "type": "remote",
      "url": "https://mcp.solucortex.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add soluai-spa-solucortex-mcp --url 'https://mcp.solucortex.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  soluai-spa-solucortex-mcp:
    url: "https://mcp.solucortex.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "soluai-spa-solucortex-mcp": {
      "Transport": "http",
      "Url": "https://mcp.solucortex.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add soluai-spa-solucortex-mcp -t streamable-http -u 'https://mcp.solucortex.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "soluai-spa-solucortex-mcp": {
      "type": "http",
      "url": "https://mcp.solucortex.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-21 (score 80, +1)

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

### 2026-09-19 (score 79, +1)

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

### 2026-09-17 (score 78, +1)

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

### 2026-09-15 (score 77, +1)

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

### 2026-09-12 (score 76, +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-09-10 (score 75, +1)

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

### 2026-09-08 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-07 (score 73, +40)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail

## MCP tools (6)

### `solucortex_recall` (~144 tokens)

Build living context for a task (POST /context/build).

    Call this at the START of a task, before touching code: returns approved, active
    memories (decisions, conventions, risks, sensitive modules, architecture) ranked by
    semantic similarity + importance. Uses OpenAI embeddings (slower, 20 req/min).

Input parameters:

- `project_id`: Project UUID. If omitted, the session default applies, else the backend infers it from the API key.
- `query` (string, required): Describe the current task/module in natural language, e.g. 'implement API key rotation in the secrets module'. Used to semantically retrieve the most relevant memories.

### `solucortex_search` (~119 tokens)

Ad-hoc semantic search of memories (POST /search/semantic).

    Use for specific questions during a task (e.g. 'how is authentication implemented?'),
    distinct from recall which builds the full startup context. Uses OpenAI embeddings
    (20 req/min).

Input parameters:

- `limit` (integer): Max memories to return.
- `project_id`: Project UUID. If omitted, the session default applies, else the backend infers it from the API key.
- `query` (string, required): Question or topic to search across the project's memories.

### `solucortex_remember` (~281 tokens)

Record a memory in SoluCortex (POST /memories).

    Call when closing a task or making a relevant technical decision. As an authorized
    agent (Bearer api_key), the memory is stored with status 'approved' and traced. Never
    store real secrets: if you find one, record location/type/severity and action taken,
    with a redacted reference.

Input parameters:

- `content` (string, required): Full content: what to remember, why it matters, where it applies and what it prevents. NEVER include real secrets (tokens, passwords, .env, credentials).
- `importance` (integer): Priority 1-10. Default 5. 6-7 high; 8-9 important decision/risk/convention; 10 critical.
- `project_id`: Project UUID. If omitted, the session default applies, else the backend infers it from the API key.
- `title` (string, required): Short, clear title (~80 chars max).
- `type` (string, required): Memory type. The backend validates the value. Canonical vocabulary: architecture, decision, risk, convention, bug_history, tech_debt, sensitive_module, learning, external_integration. (Older backends…

### `solucortex_update_memory` (~139 tokens)

Correct an existing memory (PATCH /memories/{id}).

    Agents propose, humans govern: the edit is applied but the memory returns to
    PENDING until a human re-approves it. ALWAYS tell the user the change awaits
    their approval in the SoluCortex panel. Status changes are not possible here.

Input parameters:

- `content`: Corrected full content.
- `importance`: Corrected priority 1-10.
- `memory_id` (string, required): UUID of the memory to correct.
- `title`: Corrected title.
- `type`: Corrected memory type (one of the 9 canonical types).

### `solucortex_flag_memory` (~134 tokens)

Flag a memory as outdated/incorrect (POST /memories/{id}/flag).

    The memory is marked for human review in the SoluCortex panel; nothing is
    deleted or unpublished. ALWAYS tell the user a memory awaits their decision
    in the panel. Deletion is human-only by design.

Input parameters:

- `memory_id` (string, required): UUID of the memory to flag.
- `reason` (string, required): Why it needs review: outdated, incorrect, duplicated... (10-500 chars).
- `suggested_action` (string): What you suggest the human does: update, archive, delete or review.

### `solucortex_list_memories` (~88 tokens)

List the project's memories without semantic search (GET /memories).

    Useful for quick inspection/audit or to confirm a just-created memory was stored.
    Does not consume OpenAI quota.

Input parameters:

- `limit` (integer): Max memories to return.
- `project_id`: Project UUID. If omitted, the session default applies, else the backend infers it from the API key.

## Diagnostics

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

## Score history

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

## Common questions

### What is the io.github.soluai-spa/solucortex-mcp server?

io.github.soluai-spa/solucortex-mcp is listed in the public MCP registry as io.github.soluai-spa/solucortex-mcp. Living technical memory for AI agents: recall approved project context, record what was learned. This page covers its hosted endpoint (https://mcp.solucortex.ai/mcp).

### Is the io.github.soluai-spa/solucortex-mcp server safe to use?

io.github.soluai-spa/solucortex-mcp scores 80 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 io.github.soluai-spa/solucortex-mcp server expose?

io.github.soluai-spa/solucortex-mcp exposes 6 tools: solucortex_recall, solucortex_search, solucortex_remember, solucortex_update_memory, solucortex_flag_memory, solucortex_list_memories. Their descriptions and schemas cost roughly 905 tokens of context every time the server is loaded.

### Does the io.github.soluai-spa/solucortex-mcp server require authentication?

Yes. io.github.soluai-spa/solucortex-mcp 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 io.github.soluai-spa/solucortex-mcp server still maintained?

io.github.soluai-spa/solucortex-mcp 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://mcp.solucortex.ai/mcp
- Authorisation metadata: https://mcp.solucortex.ai/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/soluai-spa/solucortex-mcp
- Changelog RSS feed: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/mcp