# Mitosislabs Mitosis MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.mitosislabs%2Fmitosis
Registry id: `mcp-registry/ai.mitosislabs/mitosis`
Status: live (checked 2026-10-26T20:43:32.733Z)

## Verdict

Mitosislabs Mitosis MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 40% of MCP servers, with 839 ms median handshake and 27 outages in 90 days. Its agent-readiness grade is A (100/100) across 20 tools, costing an agent about 3,870 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 40% of MCP servers |
| Median handshake latency | 839 ms | 30% of MCP servers |
| p95 handshake latency | 2681 ms | — |
| Checks in 30 days | 4,900 | — |
| Outages, 90 days | 27 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 100/100 (A) | 94% of MCP servers |
| Tools | 20 | — |
| Tool-list size for an agent | ~3,870 tokens | 42% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "mitosislabs-mitosis-mcp-server": {
      "type": "http",
      "url": "https://mitosislabs.ai/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http mitosislabs-mitosis-mcp-server https://mitosislabs.ai/api/mcp
```

## Tools (20)

- `cortex_accept_goal`: Saves a settled goal into the memory's goal library, along with the recipe it was designed with, and returns its goal id. Still extracts nothing: cortex_choose_
- `cortex_answer_goal`: Records the user's answer to the questions from cortex_create_goal, keyed by question id. `{"*":"skip"}` is the answer for a user who says to go ahead with what
- `cortex_ask`: Searches the user's real, private memory — the email, calendar, files, contacts and notes they have connected, plus facts agents have saved — fusing vector, ful
- `cortex_choose_enrichment`: Record what the user wants Mitosis to pull out of a data source. A newly saved source WAITS: it is stored and searchable, but nothing is extracted from it until
- `cortex_connect_link`: The connect link for one memory source, by id — email and calendar (google-workspace), WhatsApp chats, GitHub, Notion, or file uploads. Returns the canonical mi
- `cortex_connectable_sources`: Which sources this memory could connect but hasn't yet — each with what it would make answerable, routing tags, and a connect link for the user. This is what ex
- `cortex_create_goal`: Designs a goal from the user's own words: what Mitosis should pull out of their data, and how the things in it connect. Returns a read-back of what Mitosis unde
- `cortex_ingest`: Push a document into this memory so its text becomes searchable. Pass the file text as content with a filename, or several items in files (each with name and co
- `cortex_ingest_conversation`: Ingest a conversation — the user’s messages and your full answers, verbatim — into the user’s permanent memory, where it becomes searchable and appears in their
- `cortex_list_goals`: The saved goals this office already asked Mitosis to pull out of data. Call this before choosing enrichment on a new source so you can offer those goals (the us
- `cortex_manifest`: A table of contents for this user's memory: which sources are connected (email, calendar, docs, …), how many items each holds, and the top people, topics and pr
- `cortex_recall`: Semantic-only vector search over the memory, returning source excerpts. Prefer cortex_ask, which also uses full-text and graph expansion; reach for this when yo
- `cortex_remember`: Persist a fact, decision or conclusion into the memory, attributed to you. It becomes retrievable via cortex_ask immediately, in this session and every future o
- `cortex_status`: Memory health: per-source ingest and embed counts plus last sync times. Use when you need to know whether the memory is fresh or still ingesting, or when a sear
- `fetch`: Retrieve the full contents of a single item from the user’s memory by its id. Ids come from `search` results. Use this when a search result looks relevant and y
- `get_platform_status`: Get the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.
- `get_pricing`: Get current Mitosis plans, prices, credit allowances, how usage is charged, and add-ons. Use when comparing costs or recommending a plan.
- `list_skills`: List the agent skills Mitosis publishes (backup create/list/restore/health/diff/schedule/subscribe) with links to each SKILL.md manifest.
- `search`: Search the user's own private memory — their email, calendar, documents, contacts, chat history and every fact agents have remembered — and return ranked matche
- `search_docs`: Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.