io.github.soluai-spa/solucortex-mcp
PYPI · SOLUCORTEX-MCP · 2 COMPONENTS · SCANNED SEP 21
Living technical memory for AI agents: recall approved project context, record what was learned.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
pypi · solucortex-mcp
claude mcp add soluai-spa-solucortex-mcp -- uvx solucortex-mcp
{
"mcpServers": {
"soluai-spa-solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
} {
"servers": {
"soluai-spa-solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
} codex mcp add soluai-spa-solucortex-mcp -- uvx solucortex-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"soluai-spa-solucortex-mcp": {
"type": "local",
"command": [
"uvx",
"solucortex-mcp"
],
"enabled": true
}
}
} openclaw mcp add soluai-spa-solucortex-mcp --command uvx --arg solucortex-mcp
mcp_servers:
soluai-spa-solucortex-mcp:
command: "uvx"
args: ["solucortex-mcp"] {
"McpServers": {
"soluai-spa-solucortex-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"solucortex-mcp"
]
}
}
} assistant mcp add soluai-spa-solucortex-mcp -t stdio -c uvx -a solucortex-mcp
{
"mcpServers": {
"soluai-spa-solucortex-mcp": {
"command": "uvx",
"args": [
"solucortex-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 10 Sept 26 +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.
- 8 Sept 26 +36
- Injection markers: unverified → pass ▲ security
- Schema quality: 965 → 1362 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.43 ▲ functional
- MCP protocol: unverified → pass ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/solucortex-mcp@1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
solucortex_flag_memory ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | UUID of the memory to flag. |
| reason | string | yes | Why it needs review: outdated, incorrect, duplicated... (10-500 chars). |
| suggested_action | string | – | What you suggest the human does: update, archive, delete or review. |
Structured output declared, but exposes no named fields.
No examples provided.
solucortex_list_memories ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
solucortex_recall ~142
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).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | – | – | Project UUID. If omitted, the session default applies, else the backend infers it from the API key. |
| query | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
solucortex_remember ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 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 | yes | Short, clear title (~80 chars max). |
| type | string | yes | Memory type. The backend validates the value. Canonical vocabulary: architecture, decision, risk, convention, bug_history, tech_debt, sensitive_module, learning, external_integration. (Older backends… |
Structured output declared, but exposes no named fields.
No examples provided.
solucortex_search ~116
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Question or topic to search across the project's memories. |
Structured output declared, but exposes no named fields.
No examples provided.
solucortex_update_memory ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | Corrected full content. |
| importance | – | – | Corrected priority 1-10. |
| memory_id | string | yes | UUID of the memory to correct. |
| title | – | – | Corrected title. |
| type | – | – | Corrected memory type (one of the 9 canonical types). |
Structured output declared, but exposes no named fields.
No examples provided.
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.