Instadomain MCP server

• buy_domainwrite actionFree

  Start the purchase flow for an available domain via Stripe checkout. IMPORTANT: Before calling this tool, you MUST first call check_domain to get the price, then clearly show the user the price and get their explicit confirmation before proceeding. Never call buy_domain without the user seeing and approving the price first. The registrant contact details are required because the domain will be registered in the buyer's name (they become the legal owner). WHOIS privacy is enabled by default, so these details are not publicly visible. Creates a Stripe checkout session. IMPORTANT: After this tool returns, you MUST open the checkout_url by running the shell command `open "<checkout_url>"` (macOS/Linux) so the payment page launches automatically in the user's default browser. Do NOT paste the URL as a link. Tell the user the page has been opened and they can complete payment there. Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code (e.g. "US", "GB", "DE"). phone: Phone number in format +1.5551234567. org_name: Organization name (optional, leave empty for individuals). Returns: Dict with order_id, checkout_url, price_cents, and price_display.

• buy_domain_cryptowrite actionFree

  Start the purchase flow for a domain using USDC crypto payment (x402 protocol). Autonomous two-step payment flow — no browser required: Step 1: Call this tool to reserve the domain and get a pay_url. Step 2: Pay the pay_url using your x402 wallet: - If you have Coinbase Payments MCP: call its x402 payment tool with the pay_url. - Otherwise: run `curl -L <pay_url>` — your x402-enabled HTTP client will handle the 402 handshake and USDC payment on Base automatically. After payment succeeds, call get_domain_status(order_id) to poll until registration is complete (usually under 60 seconds). The registrant contact details are required because the domain will be registered in the buyer's name (they become the legal owner). WHOIS privacy is enabled by default, so these details are not publicly visible. IMPORTANT: Before calling this tool, you MUST first call check_domain to get the price and confirm it with the user. Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code (e.g. "US", "GB", "DE"). phone: Phone number in format +1.5551234567. org_name: Organization name (optional, leave empty for individuals). Returns: Dict with order_id, pay_url (full URL to pay via x402), price_usdc, price_cents, network, and USDC contract address.

• buy_domain_mppwrite actionFree

  Start the purchase flow for a domain via Stripe's Machine Payments Protocol (MPP). MPP lets autonomous agents pay with fiat (cards, Link) or stablecoins via Shared Payment Tokens, with no browser checkout. Two-step flow: Step 1: Call this tool to get an order_id and pay_url. Step 2: Make an HTTP GET request to the pay_url with an MPP-enabled HTTP client. The server responds with HTTP 402 + WWW-Authenticate; the client creates a Shared Payment Token and retries with an Authorization header. The server charges the SPT through Stripe and kicks off domain registration. After payment, call get_domain_status(order_id) to poll until complete. Requires: An MPP-compatible client configured to mint SPTs against the server's advertised Stripe Business Network profile. Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code. phone: Phone number in format +1.5551234567. org_name: Organization name (optional). Returns: Dict with order_id, pay_url (full URL), price_cents, price_display, network_id, and payment_method_types.

• check_domainFree

  Check if a domain is available for purchase and get its price. Always call this before buying. After showing the price, ask the user two things before proceeding: 1. Confirm they want to purchase at that price. 2. Which payment method they prefer: - "card" / "Stripe" → call buy_domain (opens Stripe checkout in browser) - "crypto" / "USDC" / "x402" → call buy_domain_crypto (autonomous USDC payment, no browser; requires Coinbase Payments MCP or another x402 wallet) - "MPP" / "agent pay" → call buy_domain_mpp (Stripe agent payments via Shared Payment Token, no browser) If the user has Coinbase Payments MCP configured in their session, suggest crypto as the default. Otherwise default to buy_domain (Stripe). Args: domain: The full domain name to check (e.g. "coolstartup.com"). Returns: Dict with availability status, price in cents, and formatted price.

• check_domains_bulkFree

  Check availability of up to 50 domain names in one call. Uses fast RDAP lookups (no pricing). Returns a summary with total/available/taken counts plus per-domain details. Args: domains: List of domain names to check (max 50).

• get_domain_statusFree

  Get the status of a domain purchase order. Polls the backend every 3 seconds (up to 120 seconds) until the order reaches a terminal state (complete or failed). Args: order_id: The order ID returned from buy_domain (e.g. "ord_abc123").

• get_transfer_codewrite actionFree

  Get the EPP/transfer authorization code for a completed domain purchase. Requires a transfer_token from verify_transfer_code. Args: order_id: The order ID of a completed domain purchase. transfer_token: Token returned by verify_transfer_code.

• renew_domainFree

  Renew a domain for 1 additional year. Creates a Stripe checkout session for the renewal payment. Args: order_id: The order ID of a completed domain purchase (e.g. "ord_abc123").

• request_transfer_codewrite actionFree

  Start the transfer verification flow by sending a code to the registrant's email. Always call this before get_transfer_code or unlock_domain. Then ask the user to check their email and provide the 6-digit code, then call verify_transfer_code to get a transfer_token. Args: order_id: The order ID of a completed domain purchase.

• suggest_domainsFree

  Generate domain name ideas from a keyword and check their availability. Args: keyword: A keyword or short business name (e.g. "taskflow").

• unlock_domainwrite actionFree

  Remove the registrar transfer lock. Requires a transfer_token from verify_transfer_code. Args: order_id: The order ID of a completed domain purchase. transfer_token: Token returned by verify_transfer_code.

• verify_transfer_codewrite actionFree

  Verify the email code and get a transfer token valid for 15 minutes. Call this after request_transfer_code and the user provides their code. Pass the returned transfer_token to get_transfer_code or unlock_domain. Args: order_id: The order ID of a completed domain purchase. code: The 6-digit code from the verification email.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 600ms20/20
• Tool poisoning12 tool descriptions checked3/15
• Auth qualityopen endpoint exposes 7 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Safety score

41/100

higher than 7% of 2,174 E-commerce servers

Tools

12

the typical E-commerce server has 6

Tools that change things

58%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote E-commerce server answers 100%

Response time

497 ms

faster than 31% of 1,527 E-commerce servers

Instadomain: common questions

Is Instadomain MCP server safe?

Not recommended: it is graded D (41/100). Read the Instadomain safety report

How do I install Instadomain?

It runs remotely at instadomain.fly.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Instadomain need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Instadomain maintained?

The latest release is v1.0.0.

Is Instadomain up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Instadomain?

Servers from other publishers that do the same job: Stripe MCP server, Stripe Acp MCP server and Iran Crypto Exchanges MCP server.

How does Instadomain compare with other E-commerce MCP servers?

safety score 41/100 (higher than 7% of 2,174 E-commerce servers); tools 12 (the typical E-commerce server has 6); tools that change things 58% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.