Skip to content

Blue Synergy Cortex MCP server

io.github.novotapeter-bs/cortexnovotapeter-bsssev1.0.0Scanned

Long-term, drift-free cognitive memory engine for AI Agents and Cursor IDE.

11 tools: 8 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 8 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

8 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Blue Synergy Cortex MCP server can do

The Blue Synergy Cortex MCP server is published by the GitHub account novotapeter-bs. It has 11 tools. It can create or change data (8 tools: cortex_recall, cortex_store_memory, cortex_triage_general, cortex_manage_draft and 4 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.0.

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.

11 tools

Changes things 8Claude Code: ask
  • cortex_clean_generalPromazání nebo úplné vyčištění obecné paměti ('general').No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Promazání nebo úplné vyčištění obecné paměti ('general'). Umožňuje smazat buď vše ('all'), nebo selektivně podle tématu ('by_topic') či klíčového slova ('by_keyword').
  • cortex_consolidate_projectSpustí aktualizaci a sjednocení specifikace projektu na základě nových poznámek.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Spustí aktualizaci a sjednocení specifikace projektu na základě nových poznámek.
  • cortex_create_projectZaložení nového projektu uživatelem.No findings

    Why it is in this group

    • The name "cortex_create_project" says "create": a word for a change.
    Description, as the server wrote it
    Založení nového projektu uživatelem. Umožní ukládat data pod daný project_id a přiřadí související poznámky z výchozí složky.
  • cortex_ingest_turnMANDATORNÍ PO KAŽDÉ ODPOVĚDI: Zaznamená aktuální tah konverzace do paměti Cortexu s volitelným směrováním k projektu.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    MANDATORNÍ PO KAŽDÉ ODPOVĚDI: Zaznamená aktuální tah konverzace do paměti Cortexu s volitelným směrováním k projektu.
  • cortex_manage_draftSpráva návrhu projektu: schválení ('approve') nebo zamítnutí a smazání ('reject').No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Správa návrhu projektu: schválení ('approve') nebo zamítnutí a smazání ('reject').
  • cortex_recallSémantické vyhledání v dlouhodobé paměti Cortexu.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Sémantické vyhledání v dlouhodobé paměti Cortexu. Podporuje volitelný kompaktní režim a zacílení na project_id.
  • cortex_store_memoryTrvalé uložení projektové specifikace, faktu nebo architektury pod konkrétní project_id a téma.No findings

    Why it is in this group

    • The name "cortex_store_memory" says "store": a word for a change.
    Description, as the server wrote it
    Trvalé uložení projektové specifikace, faktu nebo architektury pod konkrétní project_id a téma.
  • cortex_triage_generalRoztřídění a přesun nezařazených poznámek z výchozí složky (general) do schválených projektů.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roztřídění a přesun nezařazených poznámek z výchozí složky (general) do schválených projektů.
Only reads 3Show 3 read-only tools
  • cortex_get_project_specPřečtení aktuální specifikace projektu.No findings

    Why it is in this group

    • The name "cortex_get_project_spec" says "get": a word for reading.
    Description, as the server wrote it
    Přečtení aktuální specifikace projektu.
  • cortex_get_task_statusOvěří aktuální stav asynchronní úlohy na pozadí (např.No findings

    Why it is in this group

    • The name "cortex_get_task_status" says "get": a word for reading.
    Description, as the server wrote it
    Ověří aktuální stav asynchronní úlohy na pozadí (např. konsolidace projektu). Lze zadat buď číselné 'task_id', nebo slug 'project_id' (vrátí poslední úlohu daného projektu). Stavy: PENDING (čeká), RUNNING (probíhá), COMPLETED (hotovo), FAILED (chyba).
  • cortex_list_projectsVrátí přehledný seznam všech existujících projektů v paměti Cortex uživatele včetně jejich přesných identifikátorů (slugů) a popisů.No findings

    Why it is in this group

    • The name "cortex_list_projects" says "list": a word for reading.
    Description, as the server wrote it
    Vrátí přehledný seznam všech existujících projektů v paměti Cortex uživatele včetně jejich přesných identifikátorů (slugů) a popisů. Použij vždy, když potřebuješ zjistit přesný název projektu před zápisem nebo čtením.

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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:08 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
202
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
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
yes
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 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cortex.bluesynergy.io/v1/mcp/sse: tools/list returned 11 tools to an anonymous client, including cortex_recall (write), cortex_store_memory (write), cortex_triage_general (write), cortex_manage_draft (write), cortex_create_project (write) and 3 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 7 to 8

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools3 added, 7 changed.+3 added~7 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
    • Tools that change things, listed without credentials: 7 to 8

Install

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

claude mcp add --transport sse cortex https://cortex.bluesynergy.io/v1/mcp/sse
claude mcp add --transport sse cortex https://cortex.bluesynergy.io/v1/mcp/sse

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__cortex__cortex_get_project_spec",
      "mcp__cortex__cortex_list_projects",
      "mcp__cortex__cortex_get_task_status"
    ],
    "ask": [
      "mcp__cortex__cortex_recall",
      "mcp__cortex__cortex_store_memory",
      "mcp__cortex__cortex_triage_general",
      "mcp__cortex__cortex_manage_draft",
      "mcp__cortex__cortex_create_project",
      "mcp__cortex__cortex_consolidate_project",
      "mcp__cortex__cortex_ingest_turn",
      "mcp__cortex__cortex_clean_general"
    ],
    "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 cortex. Review it before you use it.

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.novotapeter-bs/cortex/verify?hash=c065525d6e8376f6a407b51ec554c5caff8ac45605805773d4c5d8dad2bb4043" | jq -e '.changed == false'

Pinned hash c065525d6e83, from Nov 20, 2026, 05: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.novotapeter-bs/cortex/changes.xml

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

Badge

Anlyon Radar badge for io.github.novotapeter-bs/cortex
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.novotapeter-bs/cortex.svg)](https://radar.anlyon.com/servers/io.github.novotapeter-bs/cortex)

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

Blue Synergy Cortex MCP server: questions and answers

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

Is the Blue Synergy Cortex MCP server safe?

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

Can the Blue Synergy Cortex MCP server delete data?

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

Can the Blue Synergy Cortex 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 Blue Synergy Cortex MCP server have?

11 tools: 8 write, 3 read. cortex_recall, cortex_store_memory, cortex_triage_general, cortex_manage_draft, cortex_create_project, cortex_consolidate_project, cortex_ingest_turn, cortex_clean_general and 3 more.

Does the Blue Synergy Cortex MCP server need sign-in or OAuth?

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

Does the Blue Synergy Cortex MCP server send data to outside services?

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

Has the Blue Synergy Cortex MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.