mcp-registry/io.github.nach-dakwale/instadomain · v3.1.1
As of 2026-10-25 10:38 UTC, the Nach Dakwale Instadomain MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.
Domain registration for AI agents via Stripe or x402 crypto with Cloudflare DNS.
Claude Code
claude mcp add --transport http nach-dakwale-instadomain-mcp-server https://instadomain.fly.dev/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"nach-dakwale-instadomain-mcp-server": {
"type": "http",
"url": "https://instadomain.fly.dev/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
45 parameter(s) across 12 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.nach-dakwale%2Finstadomain/fixes
{
"name": "buy_domain",
"description": "Start the purchase flow for an available domain via Stripe checkout.\n\nIMPORTANT: Before calling this tool, you MUST first call check_domain\nto get the price, then clearly show the user the price and get their\nexplicit confirmation before proceeding. Never call buy_domain without\nthe user seeing and approving the price first.\n\nThe registrant contact details are required because the domain will be\nregistered in the buyer's name (they become the legal owner). WHOIS\nprivacy is enabled by default, so",
"inputSchema": {
"type": "object",
"required": [
"domain",
"first_name",
"last_name",
"email",
"address1",
"city",
"state",
"postal_code",
"country",
"phone"
],
"properties": {
"city": {
"type": "string"
},
"email": {
"type": "string"
},
"phone": {
"type": "string"
},
"state": {
"type": "string"
},
"domain": {
"type": "string"
},
"country": {
"type": "string"
},
"address1": {
"type": "string"
},
"org_name": {
"type": "string",
"default": ""
},
"last_name": {
"type": "string"
},
"first_name": {
"type": "string"
},
"postal_code": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "buy_domain_crypto",
"description": "Start the purchase flow for a domain using USDC crypto payment (x402 protocol).\n\nAutonomous two-step payment flow — no browser required:\n\nStep 1: Call this tool to reserve the domain and get a pay_url.\nStep 2: Pay the pay_url using your x402 wallet:\n - If you have Coinbase Payments MCP: call its x402 payment tool with the pay_url.\n - Otherwise: run `curl -L <pay_url>` — your x402-enabled HTTP client will handle\n the 402 handshake and USDC payment on Base automatically.\n\nAfter payment succee",
"inputSchema": {
"type": "object",
"required": [
"domain",
"first_name",
"last_name",
"email",
"address1",
"city",
"state",
"postal_code",
"country",
"phone"
],
"properties": {
"city": {
"type": "string"
},
"email": {
"type": "string"
},
"phone": {
"type": "string"
},
"state": {
"type": "string"
},
"domain": {
"type": "string"
},
"country": {
"type": "string"
},
"address1": {
"type": "string"
},
"org_name": {
"type": "string",
"default": ""
},
"last_name": {
"type": "string"
},
"first_name": {
"type": "string"
},
"postal_code": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "buy_domain_mpp",
"description": "Start the purchase flow for a domain via Stripe's Machine Payments Protocol (MPP).\n\nMPP lets autonomous agents pay with fiat (cards, Link) or stablecoins via\nShared Payment Tokens, with no browser checkout. Two-step flow:\n\nStep 1: Call this tool to get an order_id and pay_url.\nStep 2: Make an HTTP GET request to the pay_url with an MPP-enabled HTTP\nclient. The server responds with HTTP 402 + WWW-Authenticate; the client\ncreates a Shared Payment Token and retries with an Authorization header.\nThe",
"inputSchema": {
"type": "object",
"required": [
"domain",
"first_name",
"last_name",
"email",
"address1",
"city",
"state",
"postal_code",
"country",
"phone"
],
"properties": {
"city": {
"type": "string"
},
"email": {
"type": "string"
},
"phone": {
"type": "string"
},
"state": {
"type": "string"
},
"domain": {
"type": "string"
},
"country": {
"type": "string"
},
"address1": {
"type": "string"
},
"org_name": {
"type": "string",
"default": ""
},
"last_name": {
"type": "string"
},
"first_name": {
"type": "string"
},
"postal_code": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.nach-dakwale/instadomain"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.nach-dakwale/instadomain"}) over MCP.
buy_domain_crypto ~297 tokensbuy_domain_mpp ~295 tokensbuy_domain ~294 tokenscheck_domain ~191 tokensverify_transfer_code ~154 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.nach-dakwale%2Finstadomain?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.nach-dakwale%2Finstadomain?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nach-dakwale%2Finstadomain.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nach-dakwale%2Finstadomain.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.nach-dakwale%2Finstadomain?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cff71dcf59b826ee…, first seen 2026-10-17, included at leaf 4152 of 65,508. Version history · verify what your client received.
Compare: most reliable payments servers · most reliable web servers · most reliable data servers · most reliable other servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 10:38 UTC, the Nach Dakwale Instadomain MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.
Nach Dakwale Instadomain MCP server advertises 12 tools, including buy_domain, buy_domain_crypto, buy_domain_mpp, check_domain, check_domains_bulk.
Point your MCP client at this streamable-http endpoint: https://instadomain.fly.dev/mcp/
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.