Is the Lazymac2x Diff Patch Tools MCP server down?

mcp-registry/io.github.lazymac2x/diff-patch-tools · v1.1.0

healthy
Last checked 2026-10-25 22:17 UTC · handshake 183ms

As of 2026-10-25 22:17 UTC, the Lazymac2x Diff Patch Tools MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,770
outages (90d)
0
tools
6

Cloudflare Workers MCP server: diff-patch-tools

Install Lazymac2x Diff Patch Tools MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lazymac2x-diff-patch-tools-mcp-server https://api.lazy-mac.com/diff-patch-tools/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lazymac2x-diff-patch-tools-mcp-server": {
      "type": "http",
      "url": "https://api.lazy-mac.com/diff-patch-tools/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 4 warning(s) across 6 tool(s); ~731 tokens of tool definitions.
Scores higher than 10% of 15,720 MCP servers Glimind has audited.
Its tool list costs an agent ~731 tokens per session — lighter than 85% of servers.
75 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas82
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (5)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: apply_patch, diff_stats, json_diff, patch_validate, text_diff and 1 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: apply_patch, patch_validate, three_way_merge

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: json_diff

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools/fixes

apply_patch 1 change 
{
  "name": "apply_patch",
  "description": "Apply a unified diff patch to an original text and return the patched result.",
  "inputSchema": {
    "type": "object",
    "required": [
      "original",
      "patch"
    ],
    "properties": {
      "patch": {
        "type": "string",
        "description": "Unified diff patch string"
      },
      "original": {
        "type": "string",
        "description": "Original text to patch"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
diff_stats 1 change 
{
  "name": "diff_stats",
  "description": "Parse a unified diff string and return line-level statistics: additions, deletions, hunks, files changed.",
  "inputSchema": {
    "type": "object",
    "required": [
      "diff"
    ],
    "properties": {
      "diff": {
        "type": "string",
        "description": "Unified diff string to analyse"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
json_diff 1 change 
{
  "name": "json_diff",
  "description": "Compute a structural diff between two JSON values, showing added, removed, and replaced fields.",
  "inputSchema": {
    "type": "object",
    "required": [
      "original",
      "modified"
    ],
    "properties": {
      "modified": {
        "description": "Modified JSON value (object, array, or JSON string)",
        "type": "string"
      },
      "original": {
        "description": "Original JSON value (object, array, or JSON string)",
        "type": "string"
      }
    }
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lazymac2x/diff-patch-tools"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/diff-patch-tools"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fdiff-patch-tools?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a5a490a5067a35e8…, first seen 2026-10-17, included at leaf 13310 of 68,944. Version history · verify what your client received.

Tools (6)

Compare: most reliable code servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lazymac2x Diff Patch Tools MCP server down right now?

As of 2026-10-25 22:17 UTC, the Lazymac2x Diff Patch Tools MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Lazymac2x Diff Patch Tools MCP server provide?

Lazymac2x Diff Patch Tools MCP server advertises 6 tools, including apply_patch, diff_stats, json_diff, patch_validate, text_diff.

How do I install Lazymac2x Diff Patch Tools MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/diff-patch-tools/mcp

Is the Lazymac2x Diff Patch Tools MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lazymac2x Diff Patch Tools MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve