SKYNETLAB-Cortex

endpoint

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

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is SKYNETLAB-Cortex live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is SKYNETLAB-Cortex free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does SKYNETLAB-Cortex have?

7 tools: fetch, cortex_forget, cortex_write, cortex_write_status, cortex_conflicts, cortex_recall, search.

Is SKYNETLAB-Cortex safe to connect?

Caution — its own text works on the agent reading it: poses as system instructions («You are connected to Cortex, this user's persistent memory.»). Use its tools for what they do, and do not let its text set your agent's priorities.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• fetch reads auth-required 12h ago

  Use this when a search result looks relevant and you need its full text before answering. Takes the id returned by search, and returns the memory with its url, which you cite in your answer. Do not call it with an id from anywhere else: only search results carry valid ids.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The id of a memory, exactly as returned by search"
      }
    }
  }

  arguments 12 lines copy
• cortex_forget changes data auth-required never probed

  Use this when the user asks to delete a specific memory, given the id returned by search. Ask the user to confirm before calling it: the deletion is permanent and cannot be undone. Do not use it to fix a memory that is merely out of date: saving the corrected version with cortex_write is what keeps the history.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The id of the memory to delete, exactly as returned by search"
      }
    }
  }

  arguments 12 lines copy
• cortex_write changes data auth-required never probed

  Use this whenever the user tells you to remember, note down, keep or save something, in any language. Use it as well when they state something they will need again later and would not want to repeat: a decision and the reason behind it, a stable fact about them or their work, a preference or a constraint, a conclusion they reached after effort, a correction of something believed before. Then say in one line what you saved, so they can tell you to drop it. The server rejects duplicates by itself: a refused write is not an error, do not rephrase it and try again. Do not save questions, brainstorming, passing remarks or anything the user has not actually stated, and never save passwords, tokens, keys, card numbers or other credentials, even if the user pastes them.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364

  {
    "type": "object",
    "required": [
      "title",
      "content"
    ],
    "properties": {
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "basis": {
        "enum": [
          "observed",
          "inferred"
        ],
        "type": "string",
        "description": "Origine dell'informazione: 'observed' se letta direttamente da una fonte (documento, output di uno strumento, dato reale), 'inferred' se e' una deduzione o una stima. Registrata al salvataggio e restituita al richiamo."
      },
      "title": {
        "type": "string",
        "description": "Short title, in the user's language, e.g. \"Billing service: chosen database\""
      },
      "claims": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "subject",
            "predicate",
            "object"
          ],
          "properties": {
            "object": {
              "type": "string"
            },
            "subject": {
              "type": "string"
            },
            "predicate": {
              "type": "string"
            },
            "claim_text": {
              "type": "string"
            },
            "confidence": {
              "type": "number"
            }
          }
        },
        "description": "Opzionale. Fatti atomici gia strutturati, uno per decisione o affermazione: se li passi, il rilevamento dei conflitti li usa direttamente invece di estrarli dal testo. Esempio: {subject: 'Project Vega', predicate: 'adotta', object: 'Redis'}."
      },
      "content": {
        "type": "string",
        "description": "Text to remember, in the user's language"
      },
      "event_time": {
        "type": "string",
        "description": "Optional. Set only when an explicit, unambiguous ISO 8601 date (e.g. 2026-09-28 or 2026-09-28T14:00:00Z) of the event or measurement applies to the whole memory. Never infer a date and never use the save date: omit it if unknown. Save facts from different dates as separate memories."
      }
    }
  }

  arguments 64 lines copy
• cortex_write_status reads auth-required never probed

  Use this when a previous cortex_write returned a job_id as queued and the user asks whether it was saved: returns the quality gate verdict for that job and any contradiction it opened. Do not call it for a write that already came back with a verdict.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "description": "The job_id returned by a cortex_write that came back as queued"
      }
    }
  }

  arguments 12 lines copy
• cortex_conflicts reads auth-required 22h ago

  Use this when the user asks what contradicts what in their memory, or when a memory you just read is flagged as conflicting and the user has to decide which version holds. Returns the pairs of contradicting statements with their status. Do not use it as a list of memories: it only returns detected contradictions.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• cortex_recall reads auth-required 22h ago

  Use this when the user asks about a topic as a whole ("what do you know about X", "where are we with X", "catch me up on X"): returns one narrative synthesis of the relevant memories, saying what holds now and what was superseded. Do not use it to look up a single fact or when you need sources to cite: search returns individual memories with their urls.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• search reads auth-required 22h ago

  Use this when the answer depends on the user's own context: facts about them or their work, decisions they made, preferences or constraints they stated, or anything they refer back to from an earlier conversation ("as we agreed", "my project", "the client we discussed"). Use it as well when the user asks for something done their usual way, in their format, tone, style or stack ("the way I normally write these", "my usual setup"): their way is what the memory holds. Also use it when the user asks what you know or remember about something. Returns the matching memories with id, title and url to cite; fetch returns the full text of one. Cortex is the user's own memory layer: what is saved through it stays available in the other AI apps they connect to the same account. Do not use it for general knowledge, for questions that do not depend on this particular user, or when everything needed is already in this conversation.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "What to look for, in natural language and in the user's own words, e.g. \"which database we chose for billing\""
      }
    }
  }

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.