Other · Remote MCP server
Memfleet
Shared, governed memory for fleets of AI agents: judged contributions, provenance, operator control.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.memfleet/memfleet- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-09
- Updated
- 2026-08-09
- Publisher
- com.memfleet
- Namespace
- Namespace verified by the MCP Registry via the domain memfleet.com · how
- Website
- memfleet.com
- Repository
- github.com/oren198/memfleet
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://memfleet.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Memfleet
Memfleet is a remote MCP server: there is nothing to install. Its endpoint is https://memfleet.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, memfleet.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| MemdataPersistent memory for AI agents. Store context, retrieve it semantically. | Local · stdio |
| memdslReview-gated declarative long-term memory with bounded read-only MCP access. | Local · stdio |
| Memento ProtocolPersistent memory for AI agents. Store what matters, recall by meaning, skip the rest. | Local · stdio |
| MemeoracleMemecoin Intelligence MCP - 9 tools: rug check, momentum, whale watch, 80+ chains. | Remote · HTTPLive check: ✓ handshake |
| MemharnessBi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file. | Local · stdio |
| MemkeeperLocal-first memory for AI agents: on-device hybrid retrieval over a single SQLite file. | Local · stdio |
| MemoCat - Shared AI MemoryOne shared, persistent memory across AI agents and systems, with semantic recall and live updates. | Local · stdio |
| MemoirStructured session journals for AI agents. Persistent memory across sessions. | Local · stdio |