Server definition

Hash: sha256:0f20c722891dd6586b58c1a3f3bd55987da580ab57ed5f3f7367286fbeeb2334
What it is: What a remote MCP server returned when asked what it offers: 2 tools

The blob, as servednamed by its sha256

{
  "instructions": null,
  "tools": [
    {
      "description": "Verify email deliverability in real-time. Alternative to Hunter email-verifier at 15x lower cost. Returns a structured JSON report with syntax, MX, disposable detection, role-based flags, and quality score 0-100.\n\n1. valid (boolean) -- overall verdict\n2. syntax (boolean) -- RFC 5322 format check\n3. mx (boolean) -- domain has working mail servers\n4. disposable (boolean) -- Mailinator, Guerrilla Mail, 100+ throwaway providers\n5. role (boolean) -- role-based address (admin@, info@, support@)\n6. free (boolean) -- free provider (Gmail, Yahoo, Outlook)\n7. score (number 0-100) -- composite quality score\n\nExample output: {\"valid\":true,\"syntax\":true,\"mx\":true,\"disposable\":false,\"role\":false,\"free\":true,\"score\":85,\"email\":\"[email protected]\"}\n\nUse this BEFORE sending outreach emails, adding contacts to CRM, or processing signups. Essential for verifying email deliverability, cleaning email lists, detecting fake registrations, and qualifying leads. Drop-in replacement for Hunter email verification.\n\nDo NOT use for finding emails -- use email_find_by_name instead. Do NOT use for person data -- use person_enrich_from_email instead. Do NOT use for domain deliverability audit (SPF/DKIM/DMARC) -- use email_audit_deliverability instead.",
      "inputSchema": {
        "properties": {
          "email": {
            "description": "Email address to verify (e.g. [email protected])",
            "type": "string"
          }
        },
        "required": [
          "email"
        ],
        "type": "object"
      },
      "name": "email_verify_address",
      "outputSchema": null
    },
    {
      "description": "Use this when you need to validate multiple email addresses at once (up to 100). Returns a JSON array of verification results plus summary counts.\n\n1. results (array) -- each entry has valid, syntax, mx, disposable, role, free, score\n2. summary.total (number) -- total emails processed\n3. summary.valid (number) -- count of valid emails\n4. summary.invalid (number) -- count of invalid emails\n5. summary.disposable (number) -- count of disposable addresses caught\n\nExample output: {\"results\":[{\"email\":\"[email protected]\",\"valid\":true,\"score\":90},{\"email\":\"[email protected]\",\"valid\":false,\"score\":10}],\"summary\":{\"total\":2,\"valid\":1,\"invalid\":1,\"disposable\":1}}\n\nUse this FOR bulk list cleaning, CRM hygiene, or pre-campaign validation. Essential when you have 5+ emails to verify at once.\n\nDo NOT use for single emails -- use email_verify_address instead. Do NOT use for finding emails -- use email_find_by_name instead.",
      "inputSchema": {
        "properties": {
          "emails": {
            "description": "Array of email addresses (max 100)",
            "items": {
              "type": "string"
            },
            "type": "array"
          }
        },
        "required": [
          "emails"
        ],
        "type": "object"
      },
      "name": "email_verify_batch",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:0f20c722891dd6586b58c1a3f3bd55987da580ab57ed5f3f7367286fbeeb2334 | sha256sum