Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldHostinger APIShortlist candidateTerraform MCPMCP100 Recommended
Task fit
Best for
  • Hostinger customers who want AI-assisted hosting/VPS/domain management and can isolate permissions to the required products.
  • Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for
  • Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.
  • Users who need a fully reviewed MCP100 recommendation today
Avoid when
  • Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

First-party MCP

endpoint:https: · Publisher source ↗

First-party MCP

HashiCorp · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Not documented

Popularity evidence
GitHub stars

163

GitHub stars · checked 2026-10-21

1,534

GitHub stars · checked 2026-09-25T18:35:00Z

Package downloads / 30 days

136,861

package downloads / 30 days · checked 2026-10-21

No reliable download data
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationHosted: OAuth. Local: Hostinger API token.HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
CostHostinger products and infrastructure remain billable; MCP access does not make hosting services free.HCP/TFE/run costs may apply
PermissionsThe MCP can perform real account/infrastructure actions within the authorized Hostinger account; product areas can be enabled/disabled and token/account authority matters.HCP Terraform/TFE RBAC
Data handlingHostinger account/resource data transits the hosted/local MCP and connected AI client; hosted mode is operated by Hostinger.registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs
  • Infrastructure, DNS and billing actions create a high-impact permission surface that needs stronger Recommended-grade safeguards.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk contextInfrastructure, DNS and billing actions create a high-impact permission surface that needs stronger Recommended-grade safeguards.stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review2026-10-212026-07-24
Candidate evidence2026-10-21T00:00:00Z2026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →