mcpbeat Sign in

memento Team claims MCP Server

by gitlab-memento-team-hq Your server? Claim it
answering

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.

Uptime history 9 days of history · worst day 98%
9 days agonow
98.9%
Uptime 24h
91 of 92 checks
3
Tools
read from the server
498 ms
Response time
average over 24h
open, no key
Access
streamable-http

memento Team claims missed one check this week

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.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add memento-team --transport http https://overflow.games/memento/mcp
Settings → Connectors → Add custom connector, then paste this address
https://overflow.games/memento/mcp
~/.codex/config.toml
[mcp_servers.memento-team]
url = "https://overflow.games/memento/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "memento-team": {
      "url": "https://overflow.games/memento/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "memento-team": {
      "type": "http",
      "url": "https://overflow.games/memento/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

claim
claim
Claim a path before editing it, so parallel agent sessions do not overwrite each other. ok false names the session that holds it; then work on something else or wait. A claim lasts 24 hours; claim again to renew.
release
release
Release a path this session holds, when its edit is committed.
who
who
Which session holds a path, if any.

Endpoints

URLTransportStateLatencyChecked
https://overflow.games/memento/mcp streamable-http answering 532 ms 2 min ago

Alternatives to memento Team claims

same job, measured the same way
Agent Claim MCP
by vk0dev

File-claim coordination for parallel AI coding agents: claim files before edits, no stomping.

96 installs/wk local only
Tirith
by eabz

Coordination server for parallel coding agents: claims, contracts, notices, and memory notes.

local only
Vibsync
by vibsync

One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.

answering
Marrow
by aryawidjaja

Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.

local only
D
dibs
by polymatx

Coordination for parallel coding agents: file claims, enforcement hooks, git-native lessons.

local only
Openhuddle
by nika110

Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims.

140 installs/wk local only
Jetpost
by jetpost

Notes your team and their agents build on together: write, share, comment and edit.

answering
Coordigent
by coordigent

Coding agents in one repo see each other, get warned before shared edits, and message.

172 installs/wk answering

memento Team claims — questions

Answers built from our own checks of this server.

What can memento Team claims do?
It exposes 3 tools, read directly from the server on our last check. Among them: claim, release, who. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is memento Team claims working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 498 ms. The bar chart above shows every period we have measured.
How do I connect memento Team claims?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does memento Team claims need an API key?
No. memento Team claims completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is memento Team claims?
It answers our handshake in 498 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.