A
licenseC
qualityB
maintenanceConnect any MCP-compatible AI agent to the full Hostinger platform. Manage VPS, domains, DNS, hosting, WordPress, email, ecommerce, and more through natural language.
100
6 npm
MIT
hostinger-api-mcp
Officialby hostinger
Related Servers
Alternatives to hostinger-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA stateless MCP server for the full Hostinger API, exposing 305 tools with OAuth 2.1 and API-token authentication.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides programmatic access to devil hosting platform management tools, enabling AI assistants to manage websites, databases, DNS, SSL, email, and more via a secure REST API.2AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server that bridges AI agents with external tools, APIs, databases, and services, enabling standardized tool execution and resource access.MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes all 77 ScrapingDog API endpoints as AI-ready tools, enabling web scraping, Google search, Amazon product data, LinkedIn profiles, YouTube transcripts, and more through a single API key.7738 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA proxy server that bridges AI agents and external APIs by dynamically translating OpenAPI specifications into standardized MCP tools, enabling seamless interaction without custom integration code.69MIT
TDQS
B3.2/5.0
Scored across 401 tools
Disambiguation2/5
The sheer number of tools, many of which overlap in purpose (e.g., multiple deploy/import variants, deprecated and non-deprecated versions like reach_listContactsV1 vs reach_listProfileContactsV1, and similar actions across hosting and agency-hosting), makes it difficult for an agent to select the correct one. Descriptions are detailed but the volume and duplication create significant ambiguity.
Naming Consistency2/5
Naming is inconsistent across the set: some tools have a V1 suffix, others do not; casing varies (e.g., hosting_deployJsApplication vs hosting_deployWordpressPluginV1); some tools lack a domain prefix (v2_getDomainVerificationsDIRECT); and verb usage is not uniform (e.g., list vs get vs retrieve). This mixed convention hampers predictability.
Tool Count1/5
With 401 tools, the surface is far beyond any reasonable scope for an agent to navigate effectively. Even for a comprehensive platform API, this count is excessive and will overwhelm an LLM's ability to choose correctly, leading to frequent misselection.
Completeness4/5
The API covers a broad range of Hostinger services—hosting, domains, VPS, mail, ecommerce, and marketing—with extensive CRUD and lifecycle operations. While there are a few minor gaps (e.g., no explicit tool for managing some advanced ecommerce features), overall coverage is comprehensive for the stated purpose, and the presence of deprecated tools suggests redundancy rather than missing functionality.
Maintenance
ActivityActive
ResponsivenessUnresponsive