Hostinger API MCP vs Radar
A side-by-side look at the Hostinger API MCP and Radar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hostinger API MCP for cloud platforms work over a hosted endpoint; choose Radar for cloud platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hostinger API MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
HOSTINGER_API_TOKEN, API_TOKEN, OAUTH_ISSUER, DEBUG. - You want tools like
search, execute, multi-execute.
Choose Radar when
- You need dedicated capabilities in the Cloud Platforms domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 57/100 · Good | 55/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | HOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUERDEBUG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 164 | 3,905 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Hostinger API MCP | View Radar |
Tools & capabilities
Hostinger API MCP tools 3
searchfind operations by keyword; returns each match with its `inputSchema`.executerun one operation: `{ "operation": "<name>", "params": { ... } }`.multi-executerun up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.
Radar tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"url": "https://mcp.hostinger.com"
}
}
}
Radar
No confirmed install command for Radar yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Hostinger API MCP is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Radar belongs to Cloud Platforms and uses an install path we have not confirmed yet. Pick Hostinger API MCP for cloud platforms work and Radar for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Radar has no confirmed install command yet — follow its own setup instructions.
Hostinger API MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Radar is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hostinger-api-mcp and skyhook-io-radar as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hostinger API MCP has a quality signal of 57/100 (Good) with 1 views, 0 installs and 164 GitHub stars. Radar has 55/100 (Good) with 5 views, 0 installs and 3,905 GitHub stars.