mcp server
hledit MCP
Hash-anchored file edits for MCP clients. Rejects stale writes before they happen.
Description as published by the maintainer. Source
- version 0.1.4
- active
active — Most recent push to the repository was 2026-07-14.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 1 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-14 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.4 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-09 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-09 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Palace
— last commit 2026-08-03, shares coding-agents, local-first
Local-first memory for coding agents — MCP server, single SQLite file, local embeddings
-
Memorix
— last commit 2026-08-06, shares coding-agents, local-first
Local-first persistent project memory for AI coding agents across MCP clients and sessions.
-
io.github.botzrDev/dreamd
— last commit 2026-08-05, shares coding-agents, local-first
Local-first, cross-harness memory for AI coding agents.
-
ivygrep
— last commit 2026-08-06, shares coding-agents, local-first
Local code search and task context packs for coding agents
-
CodeNib
— last commit 2026-08-06, shares coding-agents
Ranked codebase search and static symbol navigation for coding agents.
-
Trusty Squire
— last commit 2026-08-06, shares coding-agents
Trusty Squire signs up / in to websites for you so you don’t have to.
-
AI Reasoning Commons
— last commit 2026-08-06, shares coding-agents
Search, reuse, verify AI reasoning. Task marketplace with leaderboard. Zero-barrier, no auth.
-
Axis
— last commit 2026-08-03, shares coding-agents
Coding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.
-
A2CR
— last commit 2026-08-05, shares coding-agents
Save AI-agent handoff checkpoints, WorkStash notes, and WorkThreads in a local A2CR workspace.
-
io.github.aarwitz/tapp
— last commit 2026-07-30, shares coding-agents
Autonomous QA for iOS + web — agents get a deterministic ship/no-ship verdict, no test code
These share tags the maintainers applied themselves, such as coding-agents, local-first. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agent, claude-code, claude-desktop, coding-agents, context-safe, cursor, file-editing, hash-anchored, hashline, hledit, local-first, mcp, mcp-server, model-context-protocol, stale-edit, stale-write.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab