Is the Lazymac2x Api Contract Validator MCP server down?

mcp-registry/io.github.lazymac2x/api-contract-validator · v1.1.0

As of 2026-10-20 19:06 UTC, the Lazymac2x Api Contract Validator MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 9 minutes.

Cloudflare Workers MCP server: api-contract-validator

claude mcp add --transport http lazymac2x-api-contract-validator-mcp-ser https://api.lazy-mac.com/api-contract-validator/mcp

{
  "mcpServers": {
    "lazymac2x-api-contract-validator-mcp-ser": {
      "type": "http",
      "url": "https://api.lazy-mac.com/api-contract-validator/mcp"
    }
  }
}

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

Agent-readiness: B (82/100)

What to fix (3)

Auto-fix: 3 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%2Fapi-contract-validator/fixes

{
  "name": "check_breaking_changes",
  "description": "Compare two OpenAPI spec versions to detect breaking changes: removed paths/operations, new required parameters, removed response codes, operationId renames.",
  "inputSchema": {
    "type": "object",
    "required": [
      "spec_old",
      "spec_new"
    ],
    "properties": {
      "spec_new": {
        "type": "object",
        "description": "New spec version"
      },
      "spec_old": {
        "type": "object",
        "description": "Previous spec version"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "lint_api_schema",
  "description": "Lint an API spec for quality and best practice compliance. Rules: operation-id-kebab-case, response-success-required, tags-defined, no-empty-description, security-defined.",
  "inputSchema": {
    "type": "object",
    "required": [
      "spec"
    ],
    "properties": {
      "spec": {
        "type": "object",
        "description": "OpenAPI spec JSON object"
      },
      "rules": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Rules to apply (defaults to all)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "validate_openapi_spec",
  "description": "Validate an OpenAPI 3.x or AsyncAPI spec JSON. Returns structural errors, missing required fields, and warnings.",
  "inputSchema": {
    "type": "object",
    "required": [
      "spec"
    ],
    "properties": {
      "spec": {
        "type": "object",
        "description": "OpenAPI or AsyncAPI spec as a JSON object"
      },
      "strict": {
        "type": "boolean",
        "default": false,
        "description": "Treat warnings as errors (default: false)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/api-contract-validator"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/api-contract-validator"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~775 tokens).
• Tool names are unique and portable across clients.
• 99.98% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• diff_request_response ~265 tokens
• generate_mock_from_spec ~153 tokens
• lint_api_schema ~125 tokens
• check_breaking_changes ~117 tokens
• validate_openapi_spec ~115 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-contract-validator.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-contract-validator?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-contract-validator?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-contract-validator.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-contract-validator.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-contract-validator?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:56fd49625273239f…, first seen 2026-10-17, included at leaf 14418 of 34,593. Version history · verify what your client received.

Tools (5)

• check_breaking_changes
• diff_request_response
• generate_mock_from_spec
• lint_api_schema
• validate_openapi_spec

Compare: most reliable data servers · most reliable code servers

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

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

FAQ

Is the Lazymac2x Api Contract Validator MCP server down right now?

As of 2026-10-20 19:06 UTC, the Lazymac2x Api Contract Validator MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Lazymac2x Api Contract Validator MCP server provide?

Lazymac2x Api Contract Validator MCP server advertises 5 tools, including check_breaking_changes, diff_request_response, generate_mock_from_spec, lint_api_schema, validate_openapi_spec.

How do I install Lazymac2x Api Contract Validator MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/api-contract-validator/mcp

Is the Lazymac2x Api Contract Validator MCP server safe to connect to an AI agent?

Glimind scanned all 5 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 Api Contract Validator 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.