diff-patch-tools MCP server
io.github.lazymac2x/diff-patch-toolslazymac2xstreamable-httpv1.0.0Scanned
Cloudflare Workers MCP server: diff-patch-tools
6 tools: 1 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the diff-patch-tools MCP server can do
The diff-patch-tools MCP server is published by the GitHub account lazymac2x. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (three_way_merge) and create or change data (3 tools: text_diff, apply_patch and patch_validate), but cannot delete data. 2 tools only read.
2 tools read private data (text_diff and diff_stats).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
three_way_mergePerform a three-way merge of base, ours, and theirs.No findings
Why it is in this group
- The name "three_way_merge" says "merge": a word for a change that another call does not undo.
Description, as the server wrote it Perform a three-way merge of base, ours, and theirs. Conflicts are marked with standard diff3 conflict markers.
Changes things 3Claude Code: ask
apply_patchApply a unified diff patch to an original text and return the patched result.No findings
Why it is in this group
- The name "apply_patch" says "apply": a word for a change.
Description, as the server wrote it Apply a unified diff patch to an original text and return the patched result.
patch_validateCheck whether a unified diff patch can be applied cleanly to an original text without actually applying it.No findings
Why it is in this group
- The name "patch_validate" says "patch": a word for a change.
Description, as the server wrote it Check whether a unified diff patch can be applied cleanly to an original text without actually applying it.
text_diffGenerate a unified diff between two text strings.Reads private dataNo findings
Why it is in this group
- The name "text_diff" says "diff": a word for reading.
- The description's first verb is "generate": a word for a change.
What it can reach
- private-dataThe input names a file (input.original_file), and the tool reads: it reads files.
Description, as the server wrote it Generate a unified diff between two text strings. Ideal for comparing file versions before and after edits.
Only reads 2Show 2 read-only tools
diff_statsParse a unified diff string and return line-level statistics: additions, deletions, hunks, files changed.Reads private dataNo findings
Why it is in this group
- The name "diff_stats" says "diff": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it Parse a unified diff string and return line-level statistics: additions, deletions, hunks, files changed.
json_diffCompute a structural diff between two JSON values, showing added, removed, and replaced fields.No findings
Why it is in this group
- The name "json_diff" says "diff": a word for reading.
Description, as the server wrote it Compute a structural diff between two JSON values, showing added, removed, and replaced fields.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.lazy-mac.com/.well-known/oauth-protected-resource/diff-patch-tools/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.lazy-mac.com/diff-patch-tools/mcp: tools/list returned 6 tools to an anonymous client, including three_way_merge (irreversible), text_diff (write), apply_patch (write), patch_validate (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http diff-patch-tools https://api.lazy-mac.com/diff-patch-tools/mcpclaude mcp add --transport http diff-patch-tools https://api.lazy-mac.com/diff-patch-tools/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__diff-patch-tools__json_diff",
"mcp__diff-patch-tools__diff_stats"
],
"ask": [
"mcp__diff-patch-tools__text_diff",
"mcp__diff-patch-tools__apply_patch",
"mcp__diff-patch-tools__three_way_merge",
"mcp__diff-patch-tools__patch_validate"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as diff-patch-tools. Review it before you use it.
Capability tags behind 2 rules
- mcp__diff-patch-tools__text_diff private-data
- mcp__diff-patch-tools__diff_stats private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lazymac2x/diff-patch-tools/verify?hash=3348fbee527d0432696ef9fe7b7a21dfcb6205b3fc3622b4f468d81702f475bc" | jq -e '.changed == false'Pinned hash 3348fbee527d, from Nov 21, 2026, 17:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.lazymac2x/diff-patch-tools/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lazymac2x/diff-patch-tools)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:38 UTC.
diff-patch-tools MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the diff-patch-tools MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the diff-patch-tools MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the diff-patch-tools MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: three_way_merge.
What tools does the diff-patch-tools MCP server have?
- 6 tools: 1 irreversible, 3 write, 2 read. three_way_merge, text_diff, apply_patch, patch_validate, json_diff and diff_stats.
Does the diff-patch-tools MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the diff-patch-tools MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the diff-patch-tools MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.