io.github.soluai-spa/solucortex-mcp
REMOTE · MCP.SOLUCORTEX.AI · 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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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 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.
remote · mcp.solucortex.ai
claude mcp add --transport http soluai-spa-solucortex-mcp 'https://mcp.solucortex.ai/mcp'
{
"mcpServers": {
"soluai-spa-solucortex-mcp": {
"url": "https://mcp.solucortex.ai/mcp"
}
}
} {
"servers": {
"soluai-spa-solucortex-mcp": {
"type": "http",
"url": "https://mcp.solucortex.ai/mcp"
}
}
} [mcp_servers.soluai-spa-solucortex-mcp] url = "https://mcp.solucortex.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"soluai-spa-solucortex-mcp": {
"type": "remote",
"url": "https://mcp.solucortex.ai/mcp",
"enabled": true
}
}
} openclaw mcp add soluai-spa-solucortex-mcp --url 'https://mcp.solucortex.ai/mcp' --transport streamable-http
mcp_servers:
soluai-spa-solucortex-mcp:
url: "https://mcp.solucortex.ai/mcp" {
"McpServers": {
"soluai-spa-solucortex-mcp": {
"Transport": "http",
"Url": "https://mcp.solucortex.ai/mcp"
}
}
} assistant mcp add soluai-spa-solucortex-mcp -t streamable-http -u 'https://mcp.solucortex.ai/mcp'
{
"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.
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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 26 +40
- Injection markers: unverified → pass ▲ security
- 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. security
- Tool coverage: unverified → 100 ▲ functional
- 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 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 21 Sept 2026 · Probed https://mcp.solucortex.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.solucortex.ai | CN=WR3,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | RSA 2048 | SHA256-RSA | 7a537e51891430b510770f2e493cb114 |
| SANs: mcp.solucortex.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.solucortex.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| solucortex.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer
BearerProtected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.solucortex.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.solucortex.ai/mcp | HTTPS enforced | 301 | https://mcp.solucortex.ai:443/mcp |
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 ~134
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 ~88
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 ~144
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 ~281
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 ~119
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 ~139
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 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.