MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Hostinger API MCP Server

Spec Support Unverified First-party Confidence: Good (0.85)

Hostinger API MCP Server is an MCP server published by Hostinger; its MCP spec-revision support has not been verified yet. It is the first-party server from Hostinger. Last verified 2026-08-14.

Does Hostinger API MCP Server support the current MCP specification (2026-07-28)?

Undetermined. We have not verified which MCP specification revision Hostinger API MCP Server supports (as of 2026-08-14).

Is Hostinger API MCP Server a first-party (official) MCP server?

Yes. Hostinger API MCP Server is the first-party MCP server published by Hostinger (last verified 2026-08-14).

How do I connect to Hostinger API MCP Server?

Hostinger API MCP Server is available via a hosted remote endpoint at https://mcp.hostinger.com, the package npm:hostinger-api-mcp, the official MCP Registry under io.github.hostinger/hostinger-api-mcp, the source repository at https://github.com/hostinger/api-mcp-server. Authentication: oauth. Transports: streamable-http, stdio.

When were Hostinger API MCP Server's facts last verified?

2026-08-14. Each fact on this page links to the sources used to verify it.

Hostinger's API MCP server is first-party: it lives in the company's own GitHub organization, occupies the GitHub-verified io.github.hostinger registry namespace, and fronts the Hostinger hosting API. It can run locally over stdio from the hostinger-api-mcp npm package or be used as a hosted remote at mcp.hostinger.com, which the README documents as a streamable HTTP endpoint behind an OAuth prompt.

A probe of the hosted endpoint on 2026-08-14 returned a genuine OAuth bearer challenge with protected-resource metadata, so the authentication model is grounded first-hand. The registry record does not list the remote at all; it names only the npm package. The record was updated 2026-08-13 and matches npm's latest 1.35.6 exactly. No vendor surface names a supported MCP revision, so spec status is recorded as unknown.

How widely adopted is Hostinger API MCP Server?

Ranked #32 in The MCP 500 with Adoption Index 77.98 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
npm downloads (weekly) 103,839 API ·
GitHub stars 140 API ·
GitHub forks 56 API ·
Last push 2026-08-14T10:51:43Z API ·
Repository archived no API ·

How was this verified, and what are the sources?

Verified · method: registry-record · confidence 0.85 (Good).

  1. Official MCP Registry record io.github.hostinger/hostinger-api-mcp v1.35.6 (updated 2026-08-13) - "MCP server for Hostinger API", GitHub-verified namespace, npm package hostinger-api-mcp, stdio transport, repository github.com/hostinger/api-mcp-server - accessed
  2. api-mcp-server README - instructs adding "https://mcp.hostinger.com as a remote Streamable HTTP MCP server in your client's configuration and complete the OAuth prompt when it appears"; also documents local stdio use of the npm package - accessed
  3. Endpoint probe of https://mcp.hostinger.com - server/discover POST at 2026-07-28 returned HTTP 401 with WWW-Authenticate Bearer realm="mcp" and resource_metadata https://mcp.hostinger.com/.well-known/oauth-protected-resource - accessed
  4. npm package hostinger-api-mcp - latest 1.35.6 published 2026-08-13, repository field github.com/hostinger/api-mcp-server - accessed