MCP.Market

Giggal.ai MCP server

online · 100% uptime
by hassaanali723·io.github.hassaanali723/giggal-mcp·v0.2.0

Runs a deep mailbox existence check to verify catch-all, accept-all, and SEG protected emails.

A90/100grade A
What users say
No reviews yet
Be the first
Safety scan
A90/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Giggal.ai yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Giggal.ai tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 357ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 12 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 90/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Giggal.ai compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
90/100
higher than 83% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
259 ms
faster than 54% of 30,031 servers

Install Giggal.ai in Claude Code, Cursor or VS Code

claude mcp add --transport http giggal-mcp https://mcp.giggal.ai/mcp
Add to Cursor

What the publisher says

From the Giggal.ai repository's README, as published. We do not edit it. Read it on GitHub

Giggal.ai MCP Server

Available on Smithery

Verify catch-all, accept-all, and SEG-protected email addresses without leaving Claude, ChatGPT, Cursor, VS Code, or any other MCP client. This is the official Model Context Protocol server for Giggal.ai, the catch-all email verification tool that confirms the mailboxes other verifiers write off as "risky" or "unknown."

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

Why Giggal.ai

Most tools give up on the hard addresses. Giggal.ai runs a deep mailbox existence check over SMTP and returns a real deliverability result where others cannot:

  • Catch-all and accept-all domains that accept every address, even for users who do not exist
  • SEG-protected inboxes behind Proofpoint, Mimecast, and Barracuda that block the checks most verifiers rely on
  • Risky B2B contacts that competitors flag and discard, around 30% of a typical list, recovered as deliverable

99% accuracy on standard business lists and bounce rates under 3%, straight from your AI assistant.

Get an API key

Sign up at emailverifier.giggal.ai for 1,000 free verification credits, no card required, then copy your key from the Developer API tab. Claude and ChatGPT connect over OAuth and need no key. The IDE and CLI clients below use the key as a Bearer token.

Connect your AI client

Claude

Add Giggal.ai as a custom connector. No config files, no API key.

  1. Open Settings → Connectors (web or desktop).
  2. Click Add → Add custom connector.
  3. Name it Giggal.ai, paste the MCP URL, then click Add.
  4. Open the Giggal.ai connector and click Connect.
  5. Click Allow to grant verify:read (verify addresses, check credits, look up past verifications).

ChatGPT

Add Giggal.ai as a custom plugin, connected over OAuth.

  1. Open Plugins from the sidebar, then click the + in the top right.
  2. Name it Giggal.ai, set Server URL to the MCP URL, choose Authentication → OAuth, tick the confirmation, then click Create.
  3. Open the plugin, click Connect, then Sign in with Giggal.ai.
  4. Click Allow to grant verify:read.

Claude Code

claude mcp add --transport http --scope user giggal \
  https://mcp.giggal.ai/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Already have a giggal server? Run claude mcp remove giggal --scope user first, then re-add.

Cursor, Windsurf, and Cline

Add this to your MCP config file:

  • Cursor: ~/.cursor/mcp.json (or .cursor/mcp.json per project)
  • Windsurf: ~/.codeium/windsurf/mcp_config.json
  • Cline: clinemcpsettings.json (open it from the Cline MCP settings)
{
  "mcpServers": {
    "giggal": {
      "url": "https://mcp.giggal.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code

Add to .vscode/mcp.json. VS Code uses servers instead of mcpServers:

{
  "servers": {
    "giggal": {
      "url": "https://mcp.giggal.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Zed

Add to ~/.config/zed/settings.json:

{
  "context_servers": {
    "giggal": {
      "source": "custom",
      "url": "https://mcp.giggal.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Codex

Add to ~/.codex/config.toml:

[mcp_servers.giggal]
url = "https://mcp.giggal.ai/mcp"
bearer_token_env_var = "GIGGAL_API_KEY"

Codex reads the key from an env var. Set it and reload your shell, then fully quit and reopen Codex:

echo 'export GIGGAL_API_KEY="tp_live_..."' >> ~/.zshrc
source ~/.zshrc

Restart the client after adding, then just ask:

Is info@giggal.ai deliverable?

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Giggal.ai: common questions

Is Giggal.ai MCP server safe?
Yes, by our scan: it is graded A (90/100). Read the Giggal.ai safety report
How do I install Giggal.ai?
It runs remotely at mcp.giggal.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Giggal.ai need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Giggal.ai maintained?
The last commit was 14 days ago (2026-10-21). The latest release is v0.2.0.
Is Giggal.ai up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Giggal.ai compare with other MCP servers?
safety score 90/100 (higher than 83% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 259 ms (faster than 54% of 30,031 servers). Full comparison.