mergewarden
io.github.sjh9714/mergewarden
Check whether a coding agent's changes stayed inside the scope it was given.
Description as published in the official MCP registry.
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 14 | github.com/sjh9714/mergewarden |
| Last push | 2026-09-10 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 0.9.0 · active · updated 2026-07-29 | registry |
| Package | npm: mergewarden-mcp | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
npx -y mergewarden-mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- RoutineKit Capture tool workflows, save typed tools, and replay with human approval. Includes an MCP…
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/io.github.sjh9714/mergewarden)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.sjh9714/mergewarden.