Verify a professional email

You are wiring up the agntdata "Lead APIs" API to use this endpoint: Verify a professional email.

1. CONNECT over MCP (preferred). Add the superagnt MCP server, then let the client
   run OAuth on first tool call — no token to paste:
     claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp
     claude mcp login superagnt
   MCP endpoint: https://mcp.superagnt.com/mcp
   After connecting, the tool you want is named exactly:
     data_agnt_people_email_verifier
   Call agnt_tools_search or agnt_tools_list_enabled to confirm it is available.

2. REST fallback (if you are not using MCP):
     POST https://api.agntdata.dev/people/email-verifier
     Header: Authorization: Bearer <YOUR_AGNTDATA_API_KEY>
   Required parameters:
    - email (string, required)
   Optional parameters:
    - max_cost_cents (number, optional)

3. COST & KEY. This endpoint is priced per call in credits, and each successful response reports its own cost in its meta.costCents field. Only successful calls are charged.
   Get an agntdata API key at https://app.agntdata.dev.

4. TEST. Connect the server (or set the key), discover the tool
   (data_agnt_people_email_verifier), run one minimal call with just the required parameters,
   and report back the shape of the JSON response (top-level fields).

Reference (machine-readable variant): https://superagnt.com/docs/apis/lead/agnt/endpoints/people_email_verifier.md

{
  "name": "people_email_verifier",
  "description": "Verify the deliverability and reputation of an email address. Returns a normalized status (valid, accept_all, unknown, invalid) and provider-agnostic signals (smtp, mx, disposable, webmail, gibberish).",
  "parameters": {
    "type": "object",
    "properties": {
      "email": {
        "type": "string",
        "format": "email"
      },
      "max_cost_cents": {
        "type": "number",
        "minimum": 0
      }
    },
    "required": [
      "email"
    ]
  }
}