Giggal.ai

An email verification tool that runs inside Claude and ChatGPT

Giggal.ai ships a remote MCP server, so Claude, ChatGPT, Cursor, VS Code and friends can verify addresses, catch-all included, without you ever leaving the chat.

MCP URL https://mcp.giggal.ai/mcp

Works with your existing API keyCatch-all verification includedNo SDK, just an MCP URL

Connect your favourite AI.

Plug Giggal.ai into your AI agent over MCP and verify emails, catch-all included, right inside Claude, Cursor, VS Code and more.

Chat apps

Code editors

Claude

Add Giggal.ai as a custom connector in Claude. No config files, no API key to paste.

1. 1 In Claude (web or desktop), open Settings → Connectors.
2. 2 Click Add → Add custom connector.
3. 3 Name it Giggal.ai, paste the MCP URL below, then click Add.
4. 4 Open the Giggal.ai connector and click Connect.
5. 5 Click Allow to grant verify:read, which covers verifying addresses, checking credits and looking up past verifications.

https://mcp.giggal.ai/mcp

Restart the client after adding, then just ask: “Is info@giggal.ai deliverable?”

What your agent can do

Three tools, exposed the moment you connect. Just ask in plain English.

Verify any address

verify_emails

Check single emails or whole lists and get a clear valid or invalid result, catch-all and accept-all domains included, where other tools give up.

Pull full results

get_verification_details

Fetch the complete breakdown for a job, including per-address status, reason codes and deliverability scoring, without leaving your agent.

Check your credits

get_credit_balance

Ask your agent how many verification credits are left before it kicks off a large run. No dashboard round-trip.

Why the catch-all result matters more here

Around 30% of a B2B list sits on catch-all or accept-all domains, which accept mail for every possible address whether or not a mailbox was ever created. Most verifiers hand those back labelled risky, unknown or accept-all, meaning they could not tell.

That label is awkward in a dashboard. It is worse in a conversation, because the agent reports faithfully what it was given, and you end up with a reply telling you that a third of your addresses are uncertain. Which is the state you were in before you asked. Giggal.ai resolves those addresses to valid or invalid, and does the same for mailboxes behind 15 named secure email gateways including Proofpoint, Mimecast and Barracuda, so the agent has something to act on.

There is a longer write-up of how this works in practice, with example prompts, in verifying emails inside Claude and ChatGPT. Under the hood, the MCP server is powered by the same engine as the email verification API, giving your agent direct access to full SMTP checks and deep catch-all resolution.

Questions about MCP verification

Yes, once you connect an email verification tool over MCP. Giggal.ai runs a remote MCP server at https://mcp.giggal.ai/mcp that Claude Desktop and Claude Code can call directly. After it is connected you ask in plain English, for example "verify these eleven addresses and tell me which will bounce", and Claude calls the verify_emails tool and reports the result in the conversation.

Yes. The server is a standard remote MCP server, so any client that supports remote MCP can use it, including ChatGPT on the plans where connectors are enabled, Cursor, VS Code, Windsurf, Cline and Zed. There is no separate build for each client and no SDK to install.

Three things. verify_emails checks a single address or a whole list. get_verification_details pulls the full per-address breakdown for a job, including status and reason codes. get_credit_balance reports how many credits are left, which is worth asking before a large run.

The same way the rest of Giggal.ai does. Around 30% of a B2B list sits on catch-all or accept-all domains that accept mail for every possible address, and most verifiers return those labelled risky or unknown. Giggal.ai resolves them to valid or invalid, along with mailboxes behind 15 named secure email gateways such as Proofpoint, Mimecast and Barracuda, so what comes back to the agent is an answer rather than a shrug.

In the Developer API tab of the Giggal.ai app, not in Settings. Paste it into your MCP client config alongside the server URL.

No. It spends the same credits as the dashboard or the REST API: one credit for a standard address, 1.5 for a catch-all inside a run or 2 standalone. New accounts get 1,000 free credits with no card, and credits never expire.

No. MCP is the right tool when verification is a step inside something you are already doing in the conversation, such as checking a dozen contacts before drafting outreach. For a list of tens of thousands, use the bulk upload in the app or the REST API, which are built for it.

Get your API key and connect in a minute

Start with 1,000 free verification credits. No card required. Generate a key and paste the MCP URL into your agent.