Can my AI agent sign up?
REMOTE · MCP-SIGNUPS.TUPER.APP
Can an AI agent sign up to X? 58 services tested: Cloudflare, captcha, phone or terms gates.
Available components
Last scanned (11 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 327 tokens (~163/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp-signups.tuper.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp-signups.tuper.app | CN=YR1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | RSA 2048 | SHA256-RSA | 642fea62713520cd505a8ae2c5bd6d5d675 |
| SANs: mcp-signups.tuper.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-signups.tuper.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| tuper.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-signups.tuper.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-signups.tuper.app/mcp | HTTPS enforced | 301 | https://mcp-signups.tuper.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_signup_gates List sign-up gates ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gate | string | – | Filter; omit for all |
No output schema declared.
No examples provided.
lookup_signup_gate Can my AI agent sign up to this service? ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service or site name, or its domain |
No output schema declared.
No examples provided.
How do I install the Can my AI agent sign up? MCP server?
Can my AI agent sign up? is a hosted endpoint at https://mcp-signups.tuper.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp-signups.tuper.app
claude mcp add --transport http app-tuper-agent-signups 'https://mcp-signups.tuper.app/mcp'
What is the Can my AI agent sign up? MCP server?
Can my AI agent sign up? is an MCP server listed in the public MCP registry as app.tuper/agent-signups. Can an AI agent sign up to X? 58 services tested: Cloudflare, captcha, phone or terms gates. This page covers its hosted endpoint (https://mcp-signups.tuper.app/mcp).
Is the Can my AI agent sign up? MCP server safe to use?
Can my AI agent sign up? scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Can my AI agent sign up? MCP server expose?
Can my AI agent sign up? exposes 2 tools: lookup_signup_gate, list_signup_gates. Their descriptions and schemas cost roughly 171 tokens of context every time the server is loaded.
Does the Can my AI agent sign up? MCP server require authentication?
No. We connected to Can my AI agent sign up? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Can my AI agent sign up? MCP server still maintained?
Can my AI agent sign up? is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.