Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.nach-dakwale/instadomain

REMOTE · INSTADOMAIN.FLY.DEV · SCANNED SEP 20

Domain registration for AI agents via Stripe or x402 crypto with Cloudflare DNS.

Available components

remote · instadomain.fly.dev 74
0 this week 74 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2102 tokens (~175/item across 12 items; 12 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_transfer_code" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 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
Install

How do I install the io.github.nach-dakwale/instadomain MCP server?

io.github.nach-dakwale/instadomain is a hosted endpoint at https://instadomain.fly.dev/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 · instadomain.fly.dev

# add to Claude Code
claude mcp add --transport http nach-dakwale-instadomain 'https://instadomain.fly.dev/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "nach-dakwale-instadomain": {
      "url": "https://instadomain.fly.dev/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nach-dakwale-instadomain": {
      "type": "http",
      "url": "https://instadomain.fly.dev/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nach-dakwale-instadomain]
url = "https://instadomain.fly.dev/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nach-dakwale-instadomain": {
      "type": "remote",
      "url": "https://instadomain.fly.dev/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nach-dakwale-instadomain --url 'https://instadomain.fly.dev/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nach-dakwale-instadomain:
    url: "https://instadomain.fly.dev/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nach-dakwale-instadomain": {
      "Transport": "http",
      "Url": "https://instadomain.fly.dev/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add nach-dakwale-instadomain -t streamable-http -u 'https://instadomain.fly.dev/mcp/'
// mcp.json
{
  "mcpServers": {
    "nach-dakwale-instadomain": {
      "type": "http",
      "url": "https://instadomain.fly.dev/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 20 Sept 2026 · Probed https://instadomain.fly.dev/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 21 Aug 2026 19 Nov 2026 ECDSA 256 ECDSA-SHA384 688c4daf5300c51e0a5c1f6837a3a67a868
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of instadomain.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.dev. 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://instadomain.fly.dev/mcp/ Verified 200
http (plaintext) http://instadomain.fly.dev/mcp/ HTTPS enforced 301 https://instadomain.fly.dev/mcp/
MCP tools · 12 exposed · ~2,102 tokens

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 →

Tool Tokens
buy_domain ~429

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.

NameTypeReqDescription
address1stringyes–
citystringyes–
countrystringyes–
domainstringyes–
emailstringyes–
first_namestringyes–
last_namestringyes–
org_namestring––
phonestringyes–
postal_codestringyes–
statestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

buy_domain_crypto ~473

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.

NameTypeReqDescription
address1stringyes–
citystringyes–
countrystringyes–
domainstringyes–
emailstringyes–
first_namestringyes–
last_namestringyes–
org_namestring––
phonestringyes–
postal_codestringyes–
statestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

buy_domain_mpp ~407

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.

NameTypeReqDescription
address1stringyes–
citystringyes–
countrystringyes–
domainstringyes–
emailstringyes–
first_namestringyes–
last_namestringyes–
org_namestring––
phonestringyes–
postal_codestringyes–
statestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_domain ~221

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.

NameTypeReqDescription
domainstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

check_domains_bulk ~71

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).

NameTypeReqDescription
domainsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_domain_status ~78

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").

NameTypeReqDescription
order_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_transfer_code ~74

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.

NameTypeReqDescription
order_idstringyes–
transfer_tokenstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

renew_domain ~59

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").

NameTypeReqDescription
order_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

request_transfer_code ~86

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.

NameTypeReqDescription
order_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

suggest_domains ~46

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

NameTypeReqDescription
keywordstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

unlock_domain ~65

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.

NameTypeReqDescription
order_idstringyes–
transfer_tokenstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

verify_transfer_code ~93

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.

NameTypeReqDescription
codestringyes–
order_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.nach-dakwale/instadomain MCP server?

io.github.nach-dakwale/instadomain is an MCP server listed in the public MCP registry as io.github.nach-dakwale/instadomain. Domain registration for AI agents via Stripe or x402 crypto with Cloudflare DNS. This page covers its hosted endpoint (https://instadomain.fly.dev/mcp/).

Is the io.github.nach-dakwale/instadomain MCP server safe to use?

io.github.nach-dakwale/instadomain scores 74 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 io.github.nach-dakwale/instadomain MCP server expose?

io.github.nach-dakwale/instadomain exposes 12 tools: check_domain, check_domains_bulk, suggest_domains, get_domain_status, request_transfer_code, and 7 more. Their descriptions and schemas cost roughly 2,102 tokens of context every time the server is loaded.

Does the io.github.nach-dakwale/instadomain MCP server require authentication?

No. We connected to io.github.nach-dakwale/instadomain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.nach-dakwale/instadomain MCP server still maintained?

io.github.nach-dakwale/instadomain is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.