Skip to content

SignupBouncer MCP server

com.signupbouncer/checkersignupbouncer.comstreamable-httpv1.1.1Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SignupBouncer MCP server can do

The SignupBouncer MCP server is published by signupbouncer.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: check_email and explain_reason), but cannot delete data. 2 tools only read.

1 tool reads private data (lookup_burner_domain); 3 tools bring in text other people can write (check_email, lookup_burner_domain and integration_guide).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • check_emailChecks one email address, and optionally the signup's IP address, the way SignupBouncer checks a new signup.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 normalized 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. We don't store or log the email or IP address it checks. We cache the email's domain and its mail servers for up to an hour. For the rate limits we keep a keyed hash of the calling IP address, or of the account when the client sends a key, for up to 24 hours. When the client sends a key, we also keep a hash of the key in memory, and keyed hashes of the calling IP address and its network (/24 or /64), for up to two minutes. The IP hashes limit guessed keys. A valid key's hash is also stored with its account.

    Annotations the server declares

    • title: Check a signup email (and IP)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • explain_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…1 finding

    Why it is in this group

    • The name "explain_reason" says "explain": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "explain_reason" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_reason" says "explain": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain a reason code
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • 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 serv…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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 asks for code that checks or blocks signups in their app. 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.

    Annotations the server declares

    • title: Code to check signups in your stack
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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 se…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "lookup_burner_domain" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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, so a brand-new burner domain on a burner mail server is caught only by check_email. Accepts a domain or an email address.

    Annotations the server declares

    • title: Look up a burner domain
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:47 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://signupbouncer.com/mcp: tools/list returned 4 tools to an anonymous client, including check_email (write), explain_reason (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 3 to 2

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "explain_reason" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_reason" says "explain": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 removed, 4 changed.−2 removed~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 2.View diff
    • Tools that change things, listed without credentials: 3 to 2

Install

Pinned to version 1.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http checker https://signupbouncer.com/mcp
claude mcp add --transport http checker https://signupbouncer.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__checker__lookup_burner_domain",
      "mcp__checker__integration_guide"
    ],
    "ask": [
      "mcp__checker__check_email",
      "mcp__checker__explain_reason"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as checker. Review it before you use it.

Capability tags behind 3 rules
  • mcp__checker__check_email untrusted-input
  • mcp__checker__lookup_burner_domain private-data, untrusted-input
  • mcp__checker__integration_guide untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.signupbouncer/checker/verify?hash=ed48ac4352f51d6169ffad58d28b5718d34915d709dd5a3da31508476bf10612" | jq -e '.changed == false'

Pinned hash ed48ac4352f5, from Nov 14, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.signupbouncer/checker/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.signupbouncer/checker
[![Anlyon Radar](https://radar.anlyon.com/badge/com.signupbouncer/checker.svg)](https://radar.anlyon.com/servers/com.signupbouncer/checker)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

SignupBouncer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SignupBouncer MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SignupBouncer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SignupBouncer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SignupBouncer MCP server have?

4 tools: 2 write, 2 read. check_email, explain_reason, lookup_burner_domain and integration_guide.

Does the SignupBouncer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SignupBouncer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SignupBouncer MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.