Is the Lazymac2x Email Validator MCP server down?

mcp-registry/io.github.lazymac2x/email-validator · v1.0.0

Also listed as glama/lazymac2x/email-validator-api

As of 2026-10-21 17:12 UTC, the Lazymac2x Email Validator 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.

Cloudflare Workers MCP server: email-validator

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

{
  "mcpServers": {
    "lazymac2x-email-validator-mcp-server": {
      "type": "http",
      "url": "https://api.lazy-mac.com/email-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%2Femail-validator/fixes

{
  "name": "check_domain",
  "description": "Check domain reputation: MX records, SPF, DKIM, disposable detection, A record existence, and overall reputation score.",
  "inputSchema": {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "description": "Domain to check (e.g. gmail.com)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "validate_batch",
  "description": "Batch validate up to 100 email addresses at once. Returns individual results plus summary stats.",
  "inputSchema": {
    "type": "object",
    "required": [
      "emails"
    ],
    "properties": {
      "emails": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Array of email addresses (max 100)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "validate_email",
  "description": "Validate a single email address with comprehensive checks: syntax (RFC 5322), MX records, disposable domain detection, role-based detection, SPF/DKIM, typo suggestions, and risk scoring (0-100).",
  "inputSchema": {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "Email address to validate"
      }
    }
  },
  "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/email-validator"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/email-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 (~371 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• validate_email ~104 tokens
• suggest_fix ~95 tokens
• validate_batch ~87 tokens
• check_domain ~85 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%2Femail-validator.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Femail-validator?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Femail-validator.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Femail-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:7637eeeddcfd0415…, first seen 2026-10-17, included at leaf 16835 of 40,669. Version history · verify what your client received.

Tools (4)

• check_domain
• suggest_fix
• validate_batch
• validate_email

Compare: most reliable security servers · most reliable email servers

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

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

FAQ

Is the Lazymac2x Email Validator MCP server down right now?

As of 2026-10-21 17:12 UTC, the Lazymac2x Email Validator 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 Email Validator MCP server provide?

Lazymac2x Email Validator MCP server advertises 4 tools, including check_domain, suggest_fix, validate_batch, validate_email.

How do I install Lazymac2x Email Validator MCP server?

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

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

Glimind scanned all 4 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 Email 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.