Skip to content

solucortex-mcp server

io.github.soluai-spa/solucortex-mcpsoluai-spastreamable-httpv1.1.2Scanned

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

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 0
  • 2 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the solucortex-mcp server can do

The solucortex-mcp server is published by the GitHub account soluai-spa. It has 6 tools. It can create or change data (4 tools: solucortex_recall, solucortex_remember, solucortex_update_memory and solucortex_flag_memory), but cannot delete data. 2 tools only read.

6 tools bring in text other people can write (solucortex_recall, solucortex_search, solucortex_remember and 3 more).

The fixed checks matched 2 findings, 1 of them high severity (sensitive-path and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.1.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • solucortex_flag_memoryFlag a memory as outdated/incorrect (POST /memories/{id}/flag).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: SoluCortex: flag a memory for human review
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • solucortex_recallBuild living context for a task (POST /context/build).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: SoluCortex: recall task context
    • readOnlyHint: true
    • openWorldHint: true
  • solucortex_rememberRecord a memory in SoluCortex (POST /memories).Reads text others write2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • High

      The input schema at properties.content.description refers to ".env".

      Matched text

      inputSchema.properties.content.description: "...nclude real secrets (tokens, passwords, .env, credentials)."

      What this check looks for
    • Info

      The input schema at properties.content.description mentions "credentials".

      Matched text

      inputSchema.properties.content.description: "...real secrets (tokens, passwords, .env, credentials)."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: SoluCortex: record a memory
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • solucortex_update_memoryCorrect an existing memory (PATCH /memories/{id}).Reads text others writeNo findings

    Why it is in this group

    • The name "solucortex_update_memory" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: SoluCortex: update a memory (requires human re-approval)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • solucortex_list_memoriesList the project's memories without semantic search (GET /memories).Reads text others writeNo findings

    Why it is in this group

    • The name "solucortex_list_memories" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: SoluCortex: list memories
    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.solucortex.ai/mcp: tools/list returned 6 tools to an anonymous client, including solucortex_recall (write), solucortex_remember (write), solucortex_update_memory (write), solucortex_flag_memory (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high1 info
  • The input schema at properties.content.description refers to ".env".

    Matched text

    inputSchema.properties.content.description: "...nclude real secrets (tokens, passwords, .env, credentials)."

    What this check looks for
  • The input schema at properties.content.description mentions "credentials".

    Matched text

    inputSchema.properties.content.description: "...real secrets (tokens, passwords, .env, credentials)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http solucortex https://mcp.solucortex.ai/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http solucortex https://mcp.solucortex.ai/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__solucortex__solucortex_search",
      "mcp__solucortex__solucortex_list_memories"
    ],
    "ask": [
      "mcp__solucortex__solucortex_recall",
      "mcp__solucortex__solucortex_remember",
      "mcp__solucortex__solucortex_update_memory",
      "mcp__solucortex__solucortex_flag_memory"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as solucortex. Review it before you use it.

Capability tags behind 6 rules
  • mcp__solucortex__solucortex_recall untrusted-input
  • mcp__solucortex__solucortex_search untrusted-input
  • mcp__solucortex__solucortex_remember untrusted-input
  • mcp__solucortex__solucortex_update_memory untrusted-input
  • mcp__solucortex__solucortex_flag_memory untrusted-input
  • mcp__solucortex__solucortex_list_memories untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.soluai-spa/solucortex-mcp/verify?hash=a06742fd713f87661ab2d2c21a5b9be071066b38337aefe7fd1f342a403e88ff" | jq -e '.changed == false'

Pinned hash a06742fd713f, from Nov 20, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.soluai-spa/solucortex-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.soluai-spa/solucortex-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.soluai-spa/solucortex-mcp.svg)](https://radar.anlyon.com/servers/io.github.soluai-spa/solucortex-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.

solucortex-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the solucortex-mcp server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 2 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the solucortex-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the solucortex-mcp server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the solucortex-mcp server have?

6 tools: 4 write, 2 read. solucortex_recall, solucortex_remember, solucortex_update_memory, solucortex_flag_memory, solucortex_search and solucortex_list_memories.

Does the solucortex-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the solucortex-mcp server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the solucortex-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.