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

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

- Trust score: 66/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.solucortex.ai`: 80/100, [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 (this document), [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

- Registry: `pypi`
- Package: `solucortex-mcp`
- Version: `1.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1362 tokens (~227/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**: 83/100
  - Stability observed for 25 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 runs locally as a PyPI package, launched with uvx solucortex-mcp. 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 soluai-spa-solucortex-mcp -- uvx solucortex-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "soluai-spa-solucortex-mcp": {
      "command": "uvx",
      "args": [
        "solucortex-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "soluai-spa-solucortex-mcp": {
      "command": "uvx",
      "args": [
        "solucortex-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add soluai-spa-solucortex-mcp -- uvx solucortex-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "soluai-spa-solucortex-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "solucortex-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add soluai-spa-solucortex-mcp --command uvx --arg solucortex-mcp
```

### Hermes

```yaml
mcp_servers:
  soluai-spa-solucortex-mcp:
    command: "uvx"
    args: ["solucortex-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "soluai-spa-solucortex-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "solucortex-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add soluai-spa-solucortex-mcp -t stdio -c uvx -a solucortex-mcp
```

### Other

```json
{
  "mcpServers": {
    "soluai-spa-solucortex-mcp": {
      "command": "uvx",
      "args": [
        "solucortex-mcp"
      ]
    }
  }
}
```

## 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-19 (score 66, +1)

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

### 2026-09-17 (score 65, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-15 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 63, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-12 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 62, −15)

- [security regression] Malware scan: pass → unverified

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

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

### 2026-09-08 (score 76, +36)

- [security improvement] Injection markers: unverified → pass
- [functional regression] Schema quality: 965 → 1362
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.43
- [functional improvement] MCP protocol: unverified → pass

## MCP tools (6)

### `solucortex_recall` (~142 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` (~116 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` (~277 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` (~136 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` (~131 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` (~86 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: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/solucortex-mcp#diagnostics

## Score history

- 2026-09-20: 66
- 2026-09-19: 66
- 2026-09-18: 65
- 2026-09-17: 65
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 63
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 62
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 40
- 2026-09-06: 75
- 2026-09-05: 74
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 70
- 2026-09-01: 70
- 2026-08-31: 70
- 2026-08-30: 69
- 2026-08-29: 70
- 2026-08-28: 70
- 2026-08-27: 54
- 2026-08-26: 54

## 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 PyPI package (solucortex-mcp).

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

io.github.soluai-spa/solucortex-mcp scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 888 tokens of context every time the server is loaded.

### 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

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

io.github.soluai-spa/solucortex-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/solucortex-mcp/
- Socket report: https://socket.dev/pypi/package/solucortex-mcp
- Repository: https://github.com/soluai-spa/solucortex-mcp
- Changelog RSS feed: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/solucortex-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/solucortex-mcp.json
- HTML version of this page: https://verifymcp.io/servers/soluai-spa-solucortex-mcp/solucortex-mcp