CortexPlus MCP server

• Registry nameio.cortexplus/cortexplusverified in the MCP registry

The registry name sits under cortexplus.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools11
• Server calls itselfcortexplus
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 96 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer92 ms
• Space in an agent's context≈ 1,573 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsB · 88 of 100
• Typed results11 of 11 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 8 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search

  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…

• fetch

  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.

• recall

  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…

• remember

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

• memory

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

• tasks

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

• save_context

  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…

• resume

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

• context_packs

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

• signup

  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…

• connect

  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…