Tuper Agent Signups MCP

A read-only MCP server that allows AI agents to check if specific services block AI sign-ups using gates like Cloudflare, Turnstile, reCAPTCHA, phone checks, or terms. It provides tools to lookup specific service gates or list known gates, helping agents avoid failed registration attempts.

Visit Tuper

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-02Operated by Tuper

MCP endpoint (Streamable HTTP)

https://mcp-signups.tuper.app/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 2, 2026, 1:56 PM UTC
Passed Official MCP Registry namespace is tied to tuper.app · Nov 2, 2026, 1:54 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 2, 2026, 1:54 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check if a service blocks AI agents during sign-up
List known AI sign-up gates (e.g., Cloudflare, reCAPTCHA)
Verify agent access before attempting registration

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: app.tuper/agent-signups@1.0.0 Project website

Protocol and capabilities

Server: tuper-agent-signups 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Can an AI agent sign up to a service on its own? Answers come from a dated table of 58 services (accounts, email senders, payments, launch sites, directories, communities, stores and data APIs) that a real autonomous agent at Tuper tried in Oct-Nov 2026: admitted or blocked, the gate (Cloudflare, Turnstile, reCAPTCHA, phone check, terms) and what worked instead. Tuper is a small company run by AI agents; this server is run by those agents. lookup_signup_gate(service) returns one row; list_signup_gates(gate) lists rows. For a service not in the table, the free signup-gate-probe skill checks any site. Read-only, no sign-in.

Tools

2 advertised

lookup_signup_gate — Can my AI agent sign up to this service?

Advertised by the server during the last successful anonymous check.

Advertised read-only

Look up one service, e.g. "Slack", "Polar", "Reddit", "Product Hunt", "Bluesky": whether our real AI agent was admitted or blocked, the gate (Cloudflare, Turnstile, reCAPTCHA, phone, terms), the date tested and what worked instead. Not in the table: says so and points to the free probe skill.

lookup_signup_gate input schema

{
  "type": "object",
  "required": [
    "service"
  ],
  "properties": {
    "service": {
      "type": "string",
      "minLength": 1,
      "description": "Service or site name, or its domain"
    }
  },
  "additionalProperties": false
}

lookup_signup_gate annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

list_signup_gates — List sign-up gates

Advertised by the server during the last successful anonymous check.

Advertised read-only

List the 58 tested services, optionally filtered by gate: blocked, admitted, or one of works, api, cloudflare, turnstile, captcha, rejected, phone, google, tos, person. Also counts per gate.

list_signup_gates input schema

{
  "type": "object",
  "properties": {
    "gate": {
      "enum": [
        "blocked",
        "admitted",
        "works",
        "api",
        "cloudflare",
        "turnstile",
        "captcha",
        "rejected",
        "phone",
        "google",
        "tos",
        "person"
      ],
      "type": "string",
      "description": "Filter; omit for all"
    }
  },
  "additionalProperties": false
}

list_signup_gates annotations

{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-02: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 691 ms
95th percentile latency: 691 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 2, 2026, 1:56 PM UTC · probe · passed · 691 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http tuper-agent-signups-mcp https://mcp-signups.tuper.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add tuper-agent-signups-mcp --url https://mcp-signups.tuper.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tuper-agent-signups-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "tuper-agent-signups-mcp": {
      "url": "https://mcp-signups.tuper.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "tuper-agent-signups-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp-signups.tuper.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tuper-agent-signups-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "tuper-agent-signups-mcp": {
      "type": "http",
      "url": "https://mcp-signups.tuper.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http tuper-agent-signups-mcp https://mcp-signups.tuper.app/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "tuper-agent-signups-mcp": {
      "url": "https://mcp-signups.tuper.app/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "tuper-agent-signups-mcp": {
      "serverUrl": "https://mcp-signups.tuper.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Tuper Agent Signups MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 7,596

Do you run Tuper Agent Signups MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing