ai.mitosislabs/mitosis · v1.0.0 · agents-and-memory
ai.mitosislabs/mitosis is healthy: it completed an MCP handshake in 3330 ms and exposes 20 tools. It scores 60/100.
Mitosis agent-memory platform: pricing, docs search, platform status, agent skills. No auth.
Add to my toolfindr inventory →
Healthy · last checked 2026-10-14T09:00:59.774Z UTC
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-14T09:00:59.774Z | ok | 3330 ms |
| health | 17 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 5 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 8 / 10 |
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, full-text and graph retrieval with provenance. This is their current data on their work, schedule, contacts, projects, documents, decisions andcortex_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 you specifically want nearest-neighbour matches on meaning.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 projects. It is an index rather than an answer — it contains no message bodies, no dates and no content, so it establishes that a source existcortex_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 search came back empty and you need to tell the user whether that means "no data yet" or "nothing matched".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 explains a cortex_ask result that came back empty or off-topic: the source holding that answer is listed here rather than connected. Data conncortex_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 mitosislabs.ai dashboard page where the user can connect that source to their memory, as a ready markdown link. Source ids appear in `unconneccortex_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 one, from any agent the user has connected. Provenance: pass source_universal_ids from a previous cortex_ask so the fact links to its evidenccortex_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 content). Default feed is local_files. The result may carry choice.choice_required: when that is true the source is stored and searchable but 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 knowledge graph. Use it after an exchange where you gave a substantive answer: ingest that exchange (the user’s message + your complete repcortex_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 understood, with a real example from their data, and sometimes one round of questions it could not decide from the words alone. `answer_requiredcortex_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 whatever Mitosis thinks best. This is the last round: the reply carries answer_required=false and no further questions, because Mitosis asks abocortex_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_enrichment with choice=describe_goal and that id in goal_ids is what runs it on a source.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 the user answers. When any save/ingest result carries `choice.choice_required: true`, ask the user its `question` and present EXACTLY two ocortex_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 user can pick several) instead of inventing a new one. Last-used goals are first. Then pass the chosen ids as goal_ids to cortex_choose_enrichsearch Search the user's own private memory — their email, calendar, documents, contacts, chat history and every fact agents have remembered — and return ranked matches with citation ids and links. This is their current data on their work, schedule, contacts, projects, documents, decisions and history, whifetch 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 you need the whole record rather than the excerpt.get_pricing Get current Mitosis plans, prices, credit allowances, how usage is charged, and add-ons. Use when comparing costs or recommending a plan.get_platform_status Get the operational status of the Mitosis website, API, and MCP server. Use before reporting an outage or debugging connectivity.search_docs Keyword-search Mitosis documentation and product pages. Returns ranked results with URLs. Use to answer any "how do I…" question about Mitosis.list_skills List the agent skills Mitosis publishes (backup create/list/restore/health/diff/schedule/subscribe) with links to each SKILL.md manifest.