pulsemcp scanned Safe content atomic mcp-remote

Hostinger API

This MCP server provides AI assistants with direct access to Hostinger's API for comprehensive web hosting management, featuring over 100 specialized tools organized into billing, DNS, domain, and VPS management categories. Built by Hostinger's VPS team with Node.js and TypeScript, it supports both stdio and SSE transport modes, includes robust authentication with API token management, and enables operations like domain registration and availability checking, DNS zone record manipulation, VPS creation and management, firewall configuration, backup operations, and billing subscription handling. The implementation uses OpenAPI-generated tool schemas with proper parameter validation and error handling, supports both development and production deployment scenarios, and makes Hostinger's full hosting platform accessible through natural language interaction, making it valuable for automated hosting workflows, infrastructure management, and building AI assistants that need programmatic access to web hosting services without manual control panel navigation.

Cognium trust score

69%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: devops-ci
Source: PulseMCP
Repository: github.com/hostinger/api-mcp-server
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Hostinger API from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"