Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CortexPlus

REMOTE · MCP.CORTEXPLUS.IO

Personal memory layer: files, notes, messages, tasks and email, semantically indexed.

0 this week 70 Trust /100

Last scanned (14 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Recent critical change

Authorization (7 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1160 tokens (~105/item across 11 items; 11 tools + 0 resources), lean.Pass
  • 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 Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 49% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 13 Nov 26 0
    • Stability: fail → pass ▲ security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 91 to 94.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 94 to 91.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 91 to 94.

  • 7 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 94 to 91.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 94.

  • 14 Oct 26 0
    • Stability: 0.70 → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “connect” rewrote its description, which is the text the model reads security
    • Tool “signup” rewrote its description, which is the text the model reads security
    • “connect” added a required parameter “email”, so existing callers break ▼ functional
    • “connect” reworded the description of “key” cosmetic
Diagnostics

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 21 Nov 2026 · Probed https://mcp.cortexplus.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cortexplus.io CN=WE1,O=Google Trust Services,C=US 11 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA256 e89c0a275995692b0eac5a1e4f4d1a3b
SANs: cortexplus.io, mcp.cortexplus.io, *.mcp.cortexplus.io
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 mcp.cortexplus.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
cortexplus.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cortexplus.io/mcp Verified 200
http (plaintext) http://mcp.cortexplus.io/mcp Inconclusive 405
MCP tools · 11 exposed · ~999 tokens

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 →

Tool Tokens
connect ~128

Complete the CortexPlus connection with the 6-digit code the user received by email after signup. Ask the user for the code, then call this tool with the same email used in signup; never guess or invent the code. The response includes an API key that the AI platform should save in its CortexPlus connector configuration.

NameTypeReqDescription
clientstring–The name of the AI platform you are running on, e.g. ChatGPT, Claude, Cursor.
emailstringyesThe email address used in signup.
keystringyesThe 6-digit code from the CortexPlus email.
NameTypeReqDescription
apiKeystringyes–
emailstringyes–
namestringyes–

No examples provided.

context_packs ~48

List saved CortexPlus context packs, optionally filtered by AI platform.

NameTypeReqDescription
limitinteger––
platformstring–Platform filter, e.g. chatgpt or claude.
NameTypeReqDescription
packsarrayyes–

No examples provided.

fetch ~64

Retrieve the full content of one CortexPlus memory item by id, as returned by search. Health data (`saude` tag) is only included when the user has enabled sharing it with AI assistants in CortexPlus settings.

NameTypeReqDescription
idstringyesItem id from a search result.
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

memory ~51

Save a memory in CortexPlus. CortexPlus decides whether it is a note, task, or reminder and extracts the client.

NameTypeReqDescription
tagsarray––
textstringyesText to classify and save.
NameTypeReqDescription
clientstring|nullyes–
idstringyes–
memorystring|nullyes–
resolvedboolean|nullyes–
reviewstring|nullyes–
statusstring|nullyes–
titlestringyes–
typestringyes–
urlstringyes–

No examples provided.

recall ~103

Build a context block from the user's CortexPlus memory: the passages that answer a question plus their graph neighbours, already formatted as text. Prefer this over search when you intend to answer from the user's memory. Health data (`saude` tag) is only included when the user has enabled sharing it with AI assistants in CortexPlus settings.

NameTypeReqDescription
depthinteger––
limitinteger––
maxCharsinteger––
querystringyes–
NameTypeReqDescription
matchesintegeryes–
textstringyes–

No examples provided.

remember ~80

Store a note in the user's CortexPlus memory so future conversations can recall it.

NameTypeReqDescription
contentstringyes–
parentIdstring–Optional id of an existing memory to nest this one under.
tagsarray––
titlestring––
typestring–Node type, e.g. note or meeting-note.
NameTypeReqDescription
idstringyes–
titlestring––

No examples provided.

resume ~65

Load a previously saved CortexPlus context pack to resume work started in another AI conversation.

NameTypeReqDescription
idstring–Pack id, as returned by context_packs.
maxCharsinteger––
querystring–Topic to find the pack by, in natural language.
NameTypeReqDescription
matchesintegeryes–
packobject|nullyes–
textstringyes–

No examples provided.

save_context ~174

Save a handoff summary of this conversation to the user's CortexPlus memory so it can be resumed later in another AI platform. Write the summary yourself, in Markdown, covering: objective, decisions taken, current state, artifacts, next steps and constraints. Do not paste the raw transcript. Never include passwords, API keys or tokens.

NameTypeReqDescription
contentstringyesHandoff summary in Markdown.
keystringyesShort stable slug for the topic, e.g. context-pack-design. Sending the same key again updates the pack instead of creating another.
messageCountinteger––
modelstring––
platformstringyesThe AI platform you are running on, e.g. ChatGPT, Claude, Gemini, Cursor.
tagsarray––
titlestring––
NameTypeReqDescription
createdbooleanyes–
idstringyes–
redactionsarrayyes–
titlestringyes–
urlstringyes–

No examples provided.

search ~80

Search the user's CortexPlus memory and return ranked matches. Use this to find what the user has stored before answering from memory. Health data (`saude` tag) is only included when the user has enabled sharing it with AI assistants in CortexPlus settings.

NameTypeReqDescription
limitinteger––
querystringyesWhat to look for, in natural language.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

signup ~165

Create a CortexPlus account, or begin signing in to an existing one, so this conversation can use CortexPlus as the user's long-term memory and knowledge base. Ask the user for their email address, and for their name if you do not already have it, then call this tool. CortexPlus sends them a 6-digit code by email; ask the user for that code and call connect with it and the same email. Never guess or invent the email address.

NameTypeReqDescription
clientstring–The name of the AI platform you are running on, e.g. ChatGPT, Claude, Cursor.
emailstringyesThe user's email address. Ask the user; never guess or invent it.
namestring–The user's name, if it is not already known.
NameTypeReqDescription
sentbooleanyes–

No examples provided.

tasks ~41

List open CortexPlus tasks and reminders, optionally filtered by client.

NameTypeReqDescription
clientstring––
limitinteger––
statusstring––
NameTypeReqDescription
tasksarrayyes–

No examples provided.

Install

How do I install the CortexPlus MCP server?

CortexPlus is a hosted endpoint at https://mcp.cortexplus.io/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 · mcp.cortexplus.io

# add to Claude Code
claude mcp add --transport http io-cortexplus-cortexplus 'https://mcp.cortexplus.io/mcp'
Common questions

What is the CortexPlus MCP server?

CortexPlus is an MCP server listed in the public MCP registry as io.cortexplus/cortexplus. Personal memory layer: files, notes, messages, tasks and email, semantically indexed. This page covers its hosted endpoint (https://mcp.cortexplus.io/mcp).

Is the CortexPlus MCP server safe to use?

CortexPlus scores 70 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 CortexPlus MCP server expose?

CortexPlus exposes 11 tools: search, fetch, recall, remember, memory, and 6 more. Their descriptions and schemas cost roughly 999 tokens of context every time the server is loaded.

Does the CortexPlus MCP server require authentication?

No. We connected to CortexPlus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CortexPlus MCP server still maintained?

CortexPlus is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CortexPlus MCP server?

VerifyMCP ran 12 checks on CortexPlus, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CortexPlus: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.