Hostinger API MCP Server
Hostinger API MCP Server is an MCP server published by Hostinger, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Hostinger. Last verified 2026-08-20.
Does Hostinger API MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. Hostinger API MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
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-20).
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.
Does Hostinger API MCP Server support MCP revision 2025-11-25?
Yes. Hostinger API MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Hostinger API MCP Server support MCP revision 2026-07-28?
No. Hostinger API MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Hostinger API MCP Server's facts last verified?
2026-08-20. 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.
Which MCP spec revisions does Hostinger API MCP Server support?
Hostinger API MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Hostinger API MCP Server?
Ranked #100 in The MCP 500 with Adoption Index 55.40 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 1,631 | API · |
| GitHub stars | 155 | API · |
| GitHub forks | 56 | API · |
| Last push | 2026-09-15T13:22:43Z | API · |
| Repository archived | no | API · |
Repository and package signals for Hostinger API MCP Server
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 6
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Declared topics: ai, api, claude, cursor, gemini-cli-extension, hostinger, mcp — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
1.47.0- Last published
- First published
- Releases
- 168
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 7
- Unpacked size
- 2.2 MB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- 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
- 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
- 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
- npm registry metadata for hostinger-api-mcp at published version 1.45.3, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed