com.signupbouncer/checker

Est-ce que com.signupbouncer/checker est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.signupbouncer/checker » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• check_email≈ 436 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • ip · string · optionnel
    Optional IPv4 or IPv6 address the signup came from.
  • email · string · requis
    The email address to check.

  Exemple d'appel

  {"name": "check_email", "arguments": {"email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"score": 1, "network": {}, "reasons": [], "verdict": "allow", "normalized": {}, "suggestion": "texte", "data_version": "texte"}}

• explain_reason≈ 159 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · optionnel
    A reason code such as disposable_domain. Omit to list all codes.

  Exemple d'appel

  {"name": "explain_reason", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_rules≈ 242 tokens

  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 hook, the message a refused person sees, the "Why was this refused?" link, the velocity thresholds and the setting of each check. The context part lists your plan, the checks that need a higher plan, the values each check takes and the defaults. A key made for one app reads that app, so leave out "app". An older all-apps key needs "app".

  Paramètres, retour & exemple (1)

  Paramètres

  • app · string · optionnel
    The app id (app_...). Leave it out with a key made for one app. An older all-apps key needs it.

  Exemple d'appel

  {"name": "get_rules", "arguments": {"app": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• integration_guide≈ 374 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • stack · string · requis · supabase | fetch | nextjs | express | hono | python | firebase | better-auth
    The user's backend or auth stack.

  Exemple d'appel

  {"name": "integration_guide", "arguments": {"stack": "supabase"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"api": "texte", "docs": "texte", "files": [], "intro": "texte", "notes": [], "rules": "texte", "stack": "texte", "steps": [], "title": "texte"}}

• lookup_burner_domain≈ 212 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    A domain such as mailinator.com, or an email address.

  Exemple d'appel

  {"name": "lookup_burner_domain", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_rules≈ 1256 tokens

  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 marked block, and "shadow" stops refusing any. If one value is wrong, nothing changes and the answer says which. Returns the app's rules afterwards, with the settings that changed. Confirm the change with the user first. A key made for one app changes that app, so leave out "app". An older all-apps key needs "app".

  Paramètres, retour & exemple (9)

  Paramètres

  • app · string · optionnel
    The app id (app_...). Leave it out with a key made for one app. An older all-apps key needs it.
  • mode · string · optionnel · shadow | enforce
    enforce refuses signups. shadow only logs.
  • checks · object · optionnel
    Per check: "default" (our points), "off", "challenge" (always challenge) or "block" (always block, for checks that do not already block). A check above your plan keeps its setting.
  • block_at · integer · optionnel
    The score that marks block. Higher than challenge_at.
  • velocity · object · optionnel
    Earlier signups in the window before a velocity rule adds points: 0 turns one off, or 2 to 10,000. app counts this app. account counts all your apps and is 0 or at least app.
  • why_link · boolean · optionnel
    Add the "Why was this refused?" link to refusals.
  • challenge_at · integer · optionnel
    The score that marks challenge.
  • block_message · string · optionnel
    The message a refused person sees, 200 characters at most after we trim spaces from both ends. Empty restores our default, which we word to fit the reason for each refusal.
  • challenge_action · string · optionnel · allow | block
    What the Supabase hook does with a signup marked challenge.

  Exemple d'appel

  {"name": "update_rules", "arguments": {"app": "texte", "mode": "shadow", "checks": {}, "block_at": 1, "velocity": {}, "why_link": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://signupbouncer.com/mcp