memento Team claims is answering right now. Last checked 2 min ago. It exposes 3 tools.
Parallel coding agents claim a file before editing, so none overwrites another.
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
claude mcp add memento-team --transport http https://overflow.games/memento/mcp
https://overflow.games/memento/mcp
[mcp_servers.memento-team]
url = "https://overflow.games/memento/mcp"
{
"mcpServers": {
"memento-team": {
"url": "https://overflow.games/memento/mcp"
}
}
}
{
"servers": {
"memento-team": {
"type": "http",
"url": "https://overflow.games/memento/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
claim
release
who
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://overflow.games/memento/mcp | streamable-http | answering | 532 ms | 2 min ago |
File-claim coordination for parallel AI coding agents: claim files before edits, no stomping.
Coordination server for parallel coding agents: claims, contracts, notices, and memory notes.
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.
Coordination for parallel coding agents: file claims, enforcement hooks, git-native lessons.
Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims.
Notes your team and their agents build on together: write, share, comment and edit.
Coding agents in one repo see each other, get warned before shared edits, and message.
Answers built from our own checks of this server.