MCP tool reference · #179 of 563 by publishers
signup
Exposed by 15 servers from 15 publishers, read from the live servers by the Serverdex check; most of them sit in APIs & Integrations; 40% of them take a email parameter; the most-starred is SalesBlink Cold Email (23 stars).
signup(email: string, name: string, …)Parameters
share = % of the 15 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| string | 40% | 83.3% | Email address for the account | |
| name | string | 26.7% | 50% | Blog name, e.g. "travel-notes": 2–63 lowercase letters, digits and hyphens, no hyphen at either end. The host may use it in the blog URL. A taken name fails wit |
| agentName | string | 13.3% | 50% | The agent or product making the account, such as Claude Code. Names the key and is mentioned in the claim email. |
| source | string | 13.3% | 0% | Optional attribution tag for this signup (1-64 chars matching the pattern), e.g. "plugin", "www", "cli", "hn"; omit for none. Stored as the tenant's signup_sour |
| accept_terms | boolean | 6.7% | 100% | Set true only after you ask the person and they confirm they are 13 or older and accept the Terms (https://recallkitchen.com/terms), Privacy Policy (https://rec |
| address | object | 6.7% | 100% | Thai address, structured |
| agent | object | 6.7% | 100% | — |
| agent_framework | string | 6.7% | 0% | — |
| agent_id | string | 6.7% | 0% | Optional label, unique across Handoff. Letters, numbers, underscore, and hyphen. |
| billing_contact_email | string | 6.7% | 100% | Email of the person who will pay. Receives the claim link. |
| billing_contact_name | string | 6.7% | 0% | — |
| body | object | 6.7% | 100% | — |
Source: the input schema each server returns for signup, aggregated over the 15 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with signup
15 of 15 · 15 publishers · 15 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes signup |
|---|---|---|---|---|---|---|
| 1 | SalesBlink Cold Emailopen-salesblink · Business & CRM | open-salesblink | Business & CRM | 23 | yes | Signup for SalesBlink - Returns a magic sign-up link where a new user can create an account. |
| 2 | SlopIt: blogs for AI agentssimbastack-hq · Content & Publishing | simbastack-hq | Content & Publishing | 4 | yes | Create a SlopIt blog and get an API key, live URL, and onboarding text. Use this once, when you have no API key yet: every successful call creates a new blog. Set `title` to the blog's display name, e.g. the project or person's name. Email is required and is the only API-key recovery channel. Creating a blog accepts the operator's terms: https://slopit.io/legal. Afterwards, send `api_key` as a Bea |
| 3 | AgentDomainstashfeenahmed · APIs & Integrations | tashfeenahmed | APIs & Integrations | 3 | yes | Create a new AgentDomains account and get an API key. Requires no existing key. IMPORTANT: the returned api_key is shown ONCE and is never retrievable again: you must store it immediately (save it to ~/.agentdomains/config.json or set AGENTDOMAINS_API_KEY) or the account is lost. If this MCP connection has no Authorization header configured, pass the key as the 'api_key' argument on every later to |
| 4 | RentADriverefirity · Developer Tools | efirity | Developer Tools | 2 | yes | Self-serve signup for an agent/app. Returns an API key ONCE. Save it as RENTADRIVER_API_KEY. Rehearse with a sandbox (rd_test_) key; live bookings need a funded wallet. |
| 5 | Recall Kitchenrecall-kitchen · APIs & Integrations | recall-kitchen | APIs & Integrations | 2 | yes | Create a Recall Kitchen account and API key from an email. No API key or x402 payment required. Set accept_terms true only after you ask the person and they confirm they are 13 or older and accept the Terms (https://recallkitchen.com/terms), Privacy Policy (https://recallkitchen.com/privacy) and API Terms (https://recallkitchen.com/api-terms); never set it automatically or on the person's behalf. |
| 6 | Mcphostj0yen · Other | j0yen | Other | 1 | yes | Explicit signup, for a client that cannot keep a session across calls: create a tenant and receive a bearer key and namespace. Unauthenticated. Most clients never need this -- any other host.*/billing.* call from a fresh connection creates a tenant implicitly and returns its own /u/<secret>/mcp URL in the response's onboarding field. Recommended here: pass handoff: true to receive a short-lived, s |
| 7 | Unphurl123ergo · Communication | 123ergo | Communication | 1 | yes | Create a new Unphurl account. Returns an API key (shown once, store it securely). After signup, the user must check their email and click the verification link. The API key won't work for URL checks until the email is verified. Verification link expires after 24 hours. If the link expires, use the "resend_verification" tool to request a new one. The account starts with 20 free pipeline check cre |
| 8 | Output Chartsoutputcharts · Data & Analytics | outputcharts | Data & Analytics | — | yes | Create an account for a person's email and a Manage key for this agent; the person claims the account from the claim link. 5 per IP and 300 in all a day. Creates an account for the person's email, with a seven-day Solo trial and a Manage key for this agent, and emails them a claim link. The trial is once per person: a mailbox that had one (plus tags and Gmail dots count as the same mailbox), or a |
| 9 | Paneslogancsack · Files & Storage | logancsack | Files & Storage | — | yes | Creates an account or recovers access through an API-readable inbox. Codes expire in 10 minutes, with five attempts. The provider code is never returned. Limit: three requests per address, replenishing one per minute. |
| 10 | Handoff: Send Files to Users & Agentsjueluddinsf · Files & Storage | jueluddinsf | Files & Storage | — | yes | Create a Handoff account and return an API key once. No Authorization header is required. Save api_key. On later calls send Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass api_key only if you cannot set headers. share_file can create this key for you. The key is a secret. Do not put it in a file you share. |
| 11 | Wigglejamesonhussey · AI & Agents | jamesonhussey | AI & Agents | — | yes | Create an account. Returns an api_key that is your identity — store it durably; you cannot reclaim your handle without it. Auto-joins the shared 'general' and 'guestbook' rooms. |
| 12 | Keelenjamie7893 · Developer Tools | jamie7893 | Developer Tools | — | yes | Create a Keelen account (or start agent login) — emails a 6-digit code. UNAUTHENTICATED — the only tool besides verify_email that works before a bearer key is configured. `email` is where the code is sent. Flow: signup(email) -> the user reads the 6-digit code from their inbox -> verify_email(email, code) returns a reveal-once API key, stored as this server's `Authorization: B |
| 13 | ProShip Thailand Postproship1 · E-commerce & Retail | proship1 | E-commerce & Retail | — | yes | Creates a real ProShip account and shop, ready for Thailand Post EPS (thaipost0) shipping. The response contains your API token, user, and shop_id — SHOWN ONLY ONCE. Save the token into your MCP client's Authorization header. A full thaipost contract additionally requires a Thailand Post account arranged with ProShip support (multi-day human process). |
| 14 | Chessar.iochessar-io · Games & Sports | chessar-io | Games & Sports | — | yes | Get a playable API key in one call, no key needed: creates your account (owner = agentName) and key. Then reconnect to this server with "Authorization: Bearer <apiKey>" and call join with {"world":"rated"}. The key is shown once. |
| 15 | Measure.events Analyticsturbo-puffin · Data & Analytics | turbo-puffin | Data & Analytics | — | yes | Create a Measure account without a human. Starts a 14-day trial and returns an API key and tracking script; the billing contact is emailed a link to claim the account and add a card. No API key needed. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.