MCP.Market

pond MCP server

by tenequm·io.github.tenequm/pond·v0.14.5·72 stars
No reviews yet

Lossless archive and search for AI agent sessions across clients, exposed to agents over MCP.

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

72 stars

Reviews

Write one

Nobody has reviewed pond yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

pond tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How pond compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 4,460 AI and agents servers
GitHub stars
72
more than 93% of 2,711 AI and agents servers

Install pond in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the pond repository's README, as published. We do not edit it. Read it on GitHub

pond

"I know we discussed that before. Why can't I find that damn conversation?"

Pond makes every AI agent session you've ever run - Claude Code, Codex, any tool, any machine - searchable in one place.

Your agent history is already on your disk: thousands of sessions full of decisions, fixes, and dead ends - scattered across tools that can't search them. Pond ingests them all automatically and losslessly into storage you own (a local dir or your own S3 bucket), makes the whole corpus searchable and SQL-queryable, and hands that recall back to your agents over MCP - so "how did we fix this before?" is a query, not an archaeology dig. Sessions stop being locked to the tool that created them: any session can be restored into any supported client and continued there.

brew install tenequm/tap/pond   # macOS / Linux

scoop bucket add tenequm https://github.com/tenequm/scoop-bucket   # Windows
scoop install tenequm/pond

Or prompt your agent: "Please install and set up pond (see github.com/tenequm/pond)" - the full, failure-proofed version of that prompt is in Connect your agents.

A live 12k-session corpus, then a three-month-old fix found and verified against the current code (crisper MP4)

Five real recall questions, one corpus, one machine - method, raw numbers, and a rerunnable script in docs/benchmarks

Status: pre-v1. Schemas, wire shapes, and config keys are subject to breaking change until v1. Full documentation lives at pond.locker; the contract is docs/spec.md.

Quickstart

Install, run guided setup, and ingest your local sessions:

brew install tenequm/tap/pond   # macOS / Linux; Windows: Scoop or a release zip - see Install below
pond init   # guided setup: storage, adapters, MCP + agent skill, optional schedule
pond sync   # ingest and index - every enabled adapter

pond init registers pond as an MCP server for Claude Code and installs the bundled pond skill; for Codex it prints the command to run instead - restart the client afterwards so the tools load. By hand: claude mcp add -s user pond -- pond mcp, codex mcp add pond -- pond mcp; skill: mkdir -p ~/.claude/skills/pond && pond skill > ~/.claude/skills/pond/SKILL.md (that whole line is POSIX-only - mkdir -p, &&, and > all break or corrupt in Windows PowerShell 5.1; use the PowerShell block in Connect your agents). Then ask your agent - real prompts from daily use:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

pond: common questions

Is pond MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the pond safety report
Does pond need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is pond maintained?
The last commit was 41 days ago (2026-09-23). The latest release is v0.14.5.
What can I use instead of pond?
Servers from other publishers that do the same job: agent-device MCP server, LLM Sandbox MCP server and Pm Claude Skills MCP server.
How does pond compare with other AI and agents MCP servers?
safety score 88/100 (higher than 80% of 4,460 AI and agents servers); github stars 72 (more than 93% of 2,711 AI and agents servers). Full comparison.

Alternatives to pond

Same job from other publishers: the closest match first, then the best rated.

  • agent-device
    Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
    A
  • LLM Sandbox
    Securely run LLM-generated code in isolated containers across 7 languages and 3 container backends.
    A
  • Pm Claude Skills
    1310 professional Agent Skills + workflow recipes — searchable & fetchable over MCP.
    A
  • Watch Skill
    Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.
    B
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A