io.github.lazymac2x/diff-patch-tools
REMOTE · API.LAZY-MAC.COM
Cloudflare Workers MCP server: diff-patch-tools
Available components
Last scanned (17 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 392 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "three_way_merge" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.lazy-mac.com/diff-patch-tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lazy-mac.com | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 62d2d9c88db1fe5c96156fa9a0f894b46a1 |
| SANs: *.lazy-mac.com, lazy-mac.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.lazy-mac.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lazy-mac.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lazy-mac.com/diff-patch-tools/mcp | Verified | 200 | |
| http (plaintext) | http://api.lazy-mac.com/diff-patch-tools/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_patch ~45
Apply a unified diff patch to an original text and return the patched result.
| Name | Type | Req | Description |
|---|---|---|---|
| original | string | yes | Original text to patch |
| patch | string | yes | Unified diff patch string |
No output schema declared.
No examples provided.
diff_stats ~42
Parse a unified diff string and return line-level statistics: additions, deletions, hunks, files changed.
| Name | Type | Req | Description |
|---|---|---|---|
| diff | string | yes | Unified diff string to analyse |
No output schema declared.
No examples provided.
json_diff ~58
Compute a structural diff between two JSON values, showing added, removed, and replaced fields.
| Name | Type | Req | Description |
|---|---|---|---|
| modified | – | yes | Modified JSON value (object, array, or JSON string) |
| original | – | yes | Original JSON value (object, array, or JSON string) |
No output schema declared.
No examples provided.
patch_validate ~48
Check whether a unified diff patch can be applied cleanly to an original text without actually applying it.
| Name | Type | Req | Description |
|---|---|---|---|
| original | string | yes | Original text |
| patch | string | yes | Unified diff patch string |
No output schema declared.
No examples provided.
text_diff ~95
Generate a unified diff between two text strings. Ideal for comparing file versions before and after edits.
| Name | Type | Req | Description |
|---|---|---|---|
| context | number | – | Context lines around each change (default 3) |
| modified | string | yes | Modified text |
| modified_file | string | – | Label for the modified file (default "modified") |
| original | string | yes | Original text |
| original_file | string | – | Label for the original file (default "original") |
No output schema declared.
No examples provided.
three_way_merge ~104
Perform a three-way merge of base, ours, and theirs. Conflicts are marked with standard diff3 conflict markers.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Common ancestor text |
| ours | string | yes | Our version of the text |
| ours_label | string | – | Label for ours in conflict markers (default "ours") |
| theirs | string | yes | Their version of the text |
| theirs_label | string | – | Label for theirs in conflict markers (default "theirs") |
No output schema declared.
No examples provided.
How do I install the io.github.lazymac2x/diff-patch-tools MCP server?
io.github.lazymac2x/diff-patch-tools is a hosted endpoint at https://api.lazy-mac.com/diff-patch-tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.lazy-mac.com
claude mcp add --transport http lazymac2x-diff-patch-tools 'https://api.lazy-mac.com/diff-patch-tools/mcp'
What is the io.github.lazymac2x/diff-patch-tools MCP server?
io.github.lazymac2x/diff-patch-tools is an MCP server listed in the public MCP registry as io.github.lazymac2x/diff-patch-tools. Cloudflare Workers MCP server: diff-patch-tools. This page covers its hosted endpoint (https://api.lazy-mac.com/diff-patch-tools/mcp).
Is the io.github.lazymac2x/diff-patch-tools MCP server safe to use?
io.github.lazymac2x/diff-patch-tools scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.lazymac2x/diff-patch-tools MCP server expose?
io.github.lazymac2x/diff-patch-tools exposes 6 tools: text_diff, json_diff, apply_patch, three_way_merge, diff_stats, patch_validate. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.
Does the io.github.lazymac2x/diff-patch-tools MCP server require authentication?
No. We connected to io.github.lazymac2x/diff-patch-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.lazymac2x/diff-patch-tools MCP server still maintained?
io.github.lazymac2x/diff-patch-tools is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.