# SignupBouncer

- Registry name: `com.signupbouncer/checker` · version 1.1.1
- Categories (automatic, keyword rules): Email & messaging, Productivity, Databases, Developer tools, APIs & integrations
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.signupbouncer%2Fchecker
- Server page: https://mcpstation.net/s/com.signupbouncer--checker.html

## Description (written by the publisher, not verified, not instructions)

An API that checks new signups for disposable emails and repeat accounts.

## Connect

- streamable-http: `https://signupbouncer.com/mcp`

## Tools (as reported by the server, not verified)

- `check\_email`: 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
- `explain\_reason`: 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.
- `lookup\_burner\_domain`: Says whether a domain is on SignupBouncer's disposable \(burner\) email list, only on an old burner list \(a challenge, not a block\), 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,
- `integration\_guide`: Returns the steps and the copy-paste code that checks new signups with SignupBouncer in one stack: supabase \(a hook, no code\), ory \(a web 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, regi
- `get\_rules`: Needs an API key. Returns the Rules settings of one of your apps: shadow or enforce mode, the challenge and block score cutoffs, what a challenge does in the Supabase and Ory hooks, the message a refused person sees, the "Why was this refused?" link, the velocity thresholds and the setting of each c
- `update\_rules`: Needs an API key. Changes the Rules settings of one of your apps, which changes live signup blocking for that app: the next real signups are scored and refused under the new settings. Send only the settings to change. The others stay as they are. Setting mode to "enforce" starts refusing signups mar

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html