signupbouncer

endpoint

https://signupbouncer.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is signupbouncer live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is signupbouncer free to use?

Yes — the hub reached it with no key and no payment.

What tools does signupbouncer have?

4 tools: check_email, lookup_burner_domain, integration_guide, explain_reason.

Is signupbouncer safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• explain_reason open 1h ago

  Explains a signupbouncer reason code (for example disposable_domain, burner_mx, repeat_inbox, datacenter_ip): what it means, how many points it adds or whether it blocks alone, and the lowest plan on which it counts. Without a code, lists every code.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "code": {
        "type": "string",
        "description": "A reason code such as disposable_domain. Omit to list all codes."
      }
    },
    "additionalProperties": false
  }

  arguments 10 lines copy
• check_email unknown never probed

  Checks one email address, and optionally the signup's IP address, the way signupbouncer checks a new signup. Returns the result as "verdict" (allow, challenge or block), a 0-100 score, the reasons with their reason codes, the normalised inbox (Gmail dots and +tags folded) and the IP's network. When the domain looks like a typo of a big mail provider (gmial.com), "suggestion" holds the corrected address. Looks up the domain's mail servers live. Every reason is listed, including ones only paid plans count. Nothing sent is stored.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "ip": {
        "type": "string",
        "maxLength": 64,
        "description": "Optional IPv4 or IPv6 address the signup came from."
      },
      "email": {
        "type": "string",
        "maxLength": 320,
        "description": "The email address to check."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• lookup_burner_domain unknown never probed

  Says whether a domain is on signupbouncer's disposable (burner) email list, a known relay service or a free subdomain mail service, or a known real mailbox provider, and when our harvester observed it. Uses only the loaded lists, no DNS lookup, so a brand-new burner domain on a burner mail server is caught only by check_email. Accepts a domain or an email address.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "maxLength": 320,
        "description": "A domain such as mailinator.com, or an email address."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• integration_guide unknown 1h ago

  Returns the steps and the copy-paste code that checks new signups with signupbouncer in one stack: supabase (a hook, no code), fetch (any TypeScript server), nextjs, express, hono, python, firebase or better-auth. Use it when the user is building or changing a signup, register or auth flow. The code reads the API key from SIGNUPBOUNCER_API_KEY. The call has a 1.5-second limit, and any failure lets the signup through.

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "required": [
      "stack"
    ],
    "properties": {
      "stack": {
        "enum": [
          "supabase",
          "fetch",
          "nextjs",
          "express",
          "hono",
          "python",
          "firebase",
          "better-auth"
        ],
        "type": "string",
        "description": "The user's backend or auth stack."
      }
    },
    "additionalProperties": false
  }

  arguments 23 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.