All servers · Email & messaging · Databases · APIs & integrations
SignupBouncer
com.signupbouncer/checker · v1.1.1
Has write/delete toolsTools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | tools |
| Tool definitions | 6 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
An API that checks new signups for disposable emails and repeat accounts.
Connect
streamable-http · https://signupbouncer.com/mcp
claude mcp add --transport http checker https://signupbouncer.com/mcp{
"mcpServers": {
"checker": {
"url": "https://signupbouncer.com/mcp"
}
}
}Tools as reported by the server
check_emailChecks 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. Whenexplain_reasonExplains 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_domainSays 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_guideReturns 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, regiget_rulesNeeds 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 cupdate_ruleswrite/deleteNeeds 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
Tool changes
- 2026-10-22: check_email, explain_reason, lookup_burner_domain, integration_guide, get_rules, update_rules
- 2026-10-20: check_email, explain_reason, lookup_burner_domain, integration_guide, get_rules, update_rules
- 2026-10-18: check_email, explain_reason, lookup_burner_domain, integration_guide, get_rules, update_rules
- 2026-10-17: check_email, explain_reason, lookup_burner_domain, integration_guide
Website · JSON · Text for agents · Registry updated 2026-10-16