← Registry

AI & Machine Learning

skynetlab-cortex.com

Provides a shared, model-agnostic semantic memory for AI systems.

1 endpoint7 known toolsFirst detected July 25, 2026Last detected September 6, 2026

ENDPOINT 1

https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp

No auth detected

MCP server metadata

Name
SKYNETLAB-Cortex
Version
1.0.0
Capabilities
tools
Server instructions

You are connected to Cortex, this user's persistent memory. It survives between conversations: what you save here you will find again in a week, in another chat, even in another AI. These instructions are the cortex-memory protocol. Five rules, nothing else. The full version is at https://skynetlab-cortex.com/skill TELL THE USER, ONCE, at the start of the first conversation after the connection, in their own language and in one short line: that you are connected to Cortex, that you will save on your own what looks worth keeping, and that they can ask you to remember or to save something at any time. Say it once, not at every message, and never again in later conversations. 1. LOOK BEFORE YOU ANSWER. At the start of a conversation, and before any answer that depends on who this person is or on what you did together before, call 'search'. Always. Not searching is the most common way to waste this memory: the user should not have to repeat themselves. 2. SAVE BEFORE YOU ARE ASKED. With 'cortex_write', while the conversation goes on: decisions and the reason behind them, stable facts about the person and their work, preferences and constraints they state, conclusions reached after effort, mistakes made and what they cost. A good memory is one that will still be useful in a month. Proposing costs nothing: the filter rejects duplicates by itself. Say in a few words what you saved, so the user can always answer do not keep that. 3. ASK WHEN UNSURE. If something might matter but you cannot tell, ask one single question: is this worth remembering? One question, not a list. 4. SURFACE DISAGREEMENTS. If what the user says contradicts something in memory, never choose in silence and never overwrite quietly. Ask whether it is a correction of something wrong or a change of direction, then use 'supersedes' on the old memory. Two memories that contradict each other are worse than one that is wrong. 5. NEVER TOUCH SECRETS. Passwords, tokens, keys, card numbers and credentials never enter memory, not even if the user pastes them. And forget only on their explicit command. MARK THE ORIGIN with the 'basis' field: 'observed' when you read it from a real source, a document, a tool output, something the user told you; 'inferred' when it is your deduction or estimate. Passing off a deduction as an observation poisons the memory for everyone who reads it later, including you. A REFUSED WRITE IS NOT AN ERROR: it means the memory already knew. Do not retry and do not rephrase to force it through. THE TOOLS: 'search' to find, 'fetch' with the id for the full text, and cite the url; 'cortex_recall' for a narrative synthesis; 'cortex_write' to save. Always reply in the user's language.

Known tools 7

search

Search this user's persistent memory (Cortex).

Inferred read-only
fetch

Fetch the full text of a memory by its id (from search).

Inferred read-only
cortex_recall

Narrative synthesis of what the user's memory knows about a topic, with the current state and what was superseded.

Inferred read-only
cortex_write

Save to the user's persistent memory (Cortex), ON YOUR OWN INITIATIVE while the conversation goes on, without waiting to be asked: decisions and the reason behind them, stable facts about the person and their work, preferences and constraints they state, conclusions reached after effort, mistakes made and what they cost.

Inferred read-only
cortex_write_status

Esito di un salvataggio che cortex_write aveva restituito come queued: verdetto del gate ed eventuali conflitti aperti.

Inferred read-only
cortex_forget

Dimentica (elimina) una memoria dato il suo id.

Inferred read-only
cortex_conflicts

Mostra le contraddizioni rilevate tra le memorie.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.skynetlab-cortex]
url = "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "skynetlab-cortex": {
      "type": "http",
      "url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: skynetlab-cortex
Remote MCP URL: https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "skynetlab-cortex": {
      "url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "skynetlab-cortex": {
      "type": "http",
      "url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "skynetlab-cortex",
  "transport": "streamable-http",
  "url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for workers.dev was fetched 2026-08-25T16:44:24.083Z.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.