Home / MCP registry index / ai.mitosislabs/mitosis
ai.mitosislabs/mitosis
ai.mitosislabs/mitosis in the official MCP registry.
Endpoint https://mitosislabs.ai/api/mcp. Source: github.com/OperatingSystem-1/website.
The registry describes it as: Mitosis agent-memory platform: pricing, docs search, platform status, agent skills. No auth.
We read its 20 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
cortex_ask cortex_recall cortex_manifest cortex_status cortex_connectable_sources cortex_connect_link cortex_remember cortex_ingest cortex_ingest_conversation cortex_create_goal cortex_answer_goal cortex_accept_goal cortex_choose_enrichment cortex_list_goals search fetch get_pricing get_platform_status search_docs list_skills
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-mitosislabs-mitosis)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.