Cortex
REMOTE · SKYNETLAB-CORTEX-SAAS-MCP.CORTEX-320.WORKERS.DEV · SCANNED SEP 20
Patent-pending semantic memory for AI agents: quality-gated writes, conflict tracking. Free trial.
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 1624 tokens (~232/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- Structured output schemas are declared (29% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 Cortex MCP server?
Cortex is a hosted endpoint at https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/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 · skynetlab-cortex-saas-mcp.cortex-320.workers.dev
claude mcp add --transport http filippopilo-cortex 'https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp'
{
"mcpServers": {
"filippopilo-cortex": {
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
}
} {
"servers": {
"filippopilo-cortex": {
"type": "http",
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
}
} [mcp_servers.filippopilo-cortex] url = "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"filippopilo-cortex": {
"type": "remote",
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add filippopilo-cortex --url 'https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp' --transport streamable-http
mcp_servers:
filippopilo-cortex:
url: "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp" {
"McpServers": {
"filippopilo-cortex": {
"Transport": "http",
"Url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
}
} assistant mcp add filippopilo-cortex -t streamable-http -u 'https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp'
{
"mcpServers": {
"filippopilo-cortex": {
"type": "http",
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/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.
- 20 Sept 26 +11
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- 19 Sept 26 −7
- Judged manipulation: pass → unverified ▼ security
- Injection markers: fail → pass ▲ security
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → unverified ▼ functional
- 18 Sept 26 −3
- Injection markers: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cortex_conflicts” rewrote its description, which is the text the model reads security
- Tool “cortex_forget” rewrote its description, which is the text the model reads security
- Tool “cortex_recall” rewrote its description, which is the text the model reads security
- Tool “cortex_write” rewrote its description, which is the text the model reads security
- Tool “cortex_write_status” rewrote its description, which is the text the model reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 179 → 257 ▼ functional
- “cortex_forget” reworded the description of “id” cosmetic
- “cortex_write” reworded the description of “title” cosmetic
- “cortex_write_status” reworded the description of “job_id” cosmetic
- “fetch” reworded the description of “id” cosmetic
- “search” reworded the description of “query” cosmetic
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Tool “cortex_conflicts” rewrote its description, which is the text the model reads security
- Tool “cortex_forget” rewrote its description, which is the text the model reads security
- Tool “cortex_write_status” rewrote its description, which is the text the model reads security
- Schema quality: good → excellent functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cortex-320.workers.dev | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | aabeb1e58d2f35620e01ea79bfb1247c |
| SANs: cortex-320.workers.dev, *.cortex-320.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of skynetlab-cortex-saas-mcp.cortex-320.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp |
| Authorisation server | https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp | Inconclusive | 405 |
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 →
cortex_conflicts Show conflicts ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cortex_forget Forget memory ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of the memory to delete, exactly as returned by search |
No output schema declared.
No examples provided.
cortex_recall Recall & synthesize ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
cortex_write Save memory ~354
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.
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | – | 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 rest… |
| claims | array | – | 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 Veg… |
| content | string | yes | Text to remember, in the user's language |
| tags | array | – | – |
| title | string | yes | Short title, in the user's language, e.g. "Billing service: chosen database" |
No output schema declared.
No examples provided.
cortex_write_status Write status ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by a cortex_write that came back as queued |
No output schema declared.
No examples provided.
fetch Fetch memory ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of a memory, exactly as returned by search |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
search Search memories ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, in natural language and in the user's own words, e.g. "which database we chose for billing" |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
What is the Cortex MCP server?
Cortex is an MCP server listed in the public MCP registry as io.github.FilippoPilo/cortex. Patent-pending semantic memory for AI agents: quality-gated writes, conflict tracking. Free trial. This page covers its hosted endpoint (https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp).
Is the Cortex MCP server safe to use?
Cortex scores 85 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 Cortex MCP server expose?
Cortex exposes 7 tools: search, fetch, cortex_recall, cortex_write, cortex_write_status, and 2 more. Their descriptions and schemas cost roughly 1,007 tokens of context every time the server is loaded.
Does the Cortex MCP server require authentication?
Yes. Cortex 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 Cortex MCP server still maintained?
Cortex is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.