← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionOpenClaw MCP ServerMCP server securely bridging Claude with a self-hosted OpenClaw assistant.Hostinger API MCP ServerOfficial MCP server for Hostinger API.
FMRS63 / 100 · C70 / 100 · B
Reliability6 / 2011 / 20
Security and permissions13 / 2014 / 20
Maintenance15 / 2016 / 20
Documentation17 / 2015 / 20
Setup experience12 / 2014 / 20
Best for
  • Users who want to integrate self-hosted OpenClaw with Claude.
  • Users managing multiple OpenClaw instances from a unified interface.
  • Developers using Hostinger services.
  • Users who want to automate hosting tasks through AI assistants.
Not for
  • Users without an OpenClaw instance.
  • Users requiring unauthenticated production deployments.
  • Users not on Hostinger.
  • Those needing to manage other cloud providers.
Required permissions
  • Access to the OpenClaw gateway HTTP API.
  • Requires a gateway token (Bearer) for authentication.
  • Requires a Hostinger API token or OAuth authorization.
  • Can read and modify domains, hosting resources, etc., depending on token scopes.
Risks and side effects
  • Security risks in production if not properly secured (authentication must be enabled).
  • OAuth callback exposure if misconfigured; precise redirect URIs are recommended.
  • Exposing gateway URL and secrets could lead to security issues.
  • High-risk operations (e.g., deleting websites) are irreversible.
  • API token leakage could allow misuse of resources.
  • Mistakes could cause website or service outages.
Supported clientsClaude Desktop, Claude.aiClaude Desktop, Cursor, Gemini CLI
Tools7100