pond runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 18 Sep 2026.
Lossless archive and search for AI agent sessions across clients, exposed to agents over MCP.
What the code does
We read the source, 18 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
.context("failed to run `crontab -l`")?;
result = subprocess.run(cmd, capture_output=True, text=True, check=False)
execFile(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to pond
same job, measured the same wayPersistent memory for AI agents. Search, store, and recall across sessions.
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Persistent searchable memory for AI agents — save/get/search across sessions, tags.
MCP server for Aruba Central: expose AP, switch, and client status to AI assistants
Fast local full-text search for Windows files (tantivy + jieba), exposed to AI agents over MCP.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Hosted agent memory: store, search, and recall facts across sessions from any MCP client.
Persistent memory for AI assistants. Store, search, and recall across sessions.
pond — questions
Answers built from our own checks of this server.