Hostinger
Hosting and deploymentWeb hosting, domains, VPS and an AI website builder. Hostinger's official API MCP server lets AI tools act on websites, VPS, domains and DNS, email marketing, billing and ecommerce, with tools switchable per product.
Independent review. Unpaid; no partnership with Namecheap. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Domain registrar with DNS, email and SSL add-ons. Namecheap's official MCP server lets an AI assistant check and register domains and read or edit DNS records after you sign in; its API needs an eligible account and a whitelisted IP.
Judgment, not a score. Documentation checked 2026-10-18.
Connections: MCP connections · APIs · Portability and vendor lock-in.
Namecheap documents Claude support for its remote MCP server; other clients are not vendor-verified. Account consent controls tool access. Registration requires a price/payment confirmation, then an accepted confirmation token before charging a saved method or account funds. A checkout link is an alternative. Check domain ownership before retrying an uncertain purchase. source ↗
The sandbox is open to anyone. Production API access needs at least 20 domains, a $50 balance or $50 spent in the last 2 years, plus at least one whitelisted IPv4 address. API billing uses your account balance. Checked 2026-10-18. source ↗
Beast Mode accepts a CSV of up to 5,000 entries per search. Search is free; registering a selected domain is a purchase. source ↗
How Namecheap connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Namecheap has an official MCP server and Claude (incl. Claude Code) supports MCP, but Namecheap's docs don't name this pairing. Auth setup may differ. Namecheap MCP docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Namecheap publishes an API, but this pairing still needs network, authentication and execution-scope checks. Namecheap API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Namecheap is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Namecheap's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Namecheap file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Namecheap has an official MCP server and OpenAI Codex supports MCP, but Namecheap's docs don't name this pairing. Auth setup may differ. Namecheap MCP docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Namecheap publishes an API, but this pairing still needs network, authentication and execution-scope checks. Namecheap API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Namecheap is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Namecheap's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Namecheap file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Namecheap has an official MCP server and Google Antigravity supports MCP, but Namecheap's docs don't name this pairing. Auth setup may differ. Namecheap MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Namecheap publishes an API, but this pairing still needs network, authentication and execution-scope checks. Namecheap API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Namecheap is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Namecheap's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Namecheap file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
No long-form review yet. Verdict is based on research, not hands-on testing.