io.github.daedalus/mcp-external-memory
External Memory
Is the io.github.daedalus/mcp-external-memory MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-11-02.
An MCP server that gives LLMs persistent, searchable semantic memory
needs mcp<2 probed 2026-11-14 · unchanged since 2026-11-02
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-11-02.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' mcp-external-memory@0.1.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- External Memory 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/daedalus/mcp-external-memory
- Registry
- active, updated 2026-04-13 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| memory_update | 234 | 23 % |
| memory_store | 213 | 21 % |
| memory_search | 208 | 21 % |
| memory_list | 174 | 17 % |
| memory_get | 69 | 7 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.daedalus/mcp-delonghi-ecam · crashed on start
- io.github.daedalus/mcp-ecdsa · needs mcp<2
- io.github.daedalus/mcp-epochs · needs mcp<2
- io.github.daedalus/mcp-exa · alive
- io.github.daedalus/mcp-gdbserver · crashed on start
- io.github.daedalus/mcp-hashlib · alive
- io.github.daedalus/mcp-homeassistant · crashed on start
- io.github.daedalus/mcp-kicad · alive
Servers that mention external.
- AIﾉアカリ☆ Agent Trust Receipt ai.ai-akari/agent-trust-receipt · paid (402)
- com.agenticpaywall/composer · alive
- Decision Anchor com.decision-anchor/da · alive
- Signal-One by EMETZOR com.emetzor/signal-one · no DNS
- Mailbuttons com.mailbuttons/mcp-server · alive
- com.seoapi/meta · rate limited
- Siglume MCP Gateway com.siglume/mcp-gateway · alive
- FINLY Balance Report Analysis il.co.finly/report-analysis · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-02 08:20 | needs mcp<2 | 1.4 s | 7 | 1.8k | 1.0k |
| 2026-10-19 07:00 | install failed |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'