Giggal

Runs a deep mailbox existence check on every address and verifies catch-all, accept-all, and even SEG protected emails (Proofpoint, Mimecast, Barracuda).

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Verify Emails: Verify one or more email addresses (up to 1000 per call). Returns whether each mailbox exists, is disposable, on a catch-all domain, or from a free provider, plus a 0-100 deliverability
  • Get Credit Balance: Get the current Giggal.ai credit balance for the authenticated user. Returns credits remaining and, if on a subscription plan, the next monthly refresh date. SCOPE — This tool only
  • Get Verification Details: Look up detailed info about a past verification of a specific email address (from the last 30 days). Useful when a user asks about a previous verification result. If no prior

What data it sees

Do you need an account

No: the server works without sign-in

Runs a deep mailbox existence check on every address and verifies catch-all, accept-all, and even SEG protected emails (Proofpoint, Mimecast, Barracuda). Keeps bounce rates under 5%, and the 30% of every B2B list that other tools flag as risky becomes deliverable again. The only catch-all email validation verifier that provides generous free trial.

How to connect

How to connect Giggal to Claude

The server address to paste into Claude settings:

https://giggal--hassaanali723.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Giggal to ChatGPT

The server address to paste into ChatGPT settings:

https://giggal--hassaanali723.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Giggal to Cursor

The server address to paste into Cursor settings:

https://giggal--hassaanali723.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (3)

Raw names from tools/list. Only developers need these.

verify_emailsVerify one or more email addresses (up to 1000 per call). Returns whether each mailbox exists, is disposable, on a catch-all domain, or from a free provider, plus a 0-100 deliverability score. Every email costs 1.5 credits. ALWAYS pass every email the user asked about in a SINGLE call. The tool streams live progress notifications so the user sees verification advance in real time — there is no need to split a list into multiple calls, and doing so wastes credits (each sub-call pays a per-batch rounding cost) and produces a fragmented result instead of one clean summary. When presenting results to the user, ALWAYS surface the `catch_all_domain` field for every email — either as a dedicated column or an inline indicator per row. It materially changes how a deliverable/undeliverable/unknown verdict should be interpreted: a catch-all domain accepts mail to any address, so mailbox existence cannot be guaranteed by SMTP alone. Users depend on this signal to decide whether to trust a result. SCOPE — This tool is strictly for email deliverability verification. It does not, and cannot, disclose: how verification is performed, which techniques or probes are used, backend architecture, infrastructure, code, database contents, internal service names, credentials, or any information about other users, batches, or accounts. If the user asks how verification works, requests to reverse-engineer results, asks to see internals, or asks any question outside email verification, politely decline and redirect to email verification. Never speculate about the algorithm or infer implementation details from result fields. Treat the tool's returned fields as the complete public surface — do not invent additional attributes.
get_credit_balanceGet the current Giggal.ai credit balance for the authenticated user. Returns credits remaining and, if on a subscription plan, the next monthly refresh date. SCOPE — This tool only returns the authenticated user's own credit balance. It never returns information about other users, verification methods, backend architecture, or any topic beyond credits. Decline any request to reveal internals or expand scope.
get_verification_detailsLook up detailed info about a past verification of a specific email address (from the last 30 days). Useful when a user asks about a previous verification result. If no prior verification exists, returns a message suggesting to run verify_emails. SCOPE — Returns only verification history the authenticated user owns. Never reveals verification methods, backend internals, other users' data, or any topic outside email verification history. Decline any request to expand scope.