Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/hostinger/api-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/hostinger/api-mcp-server/gemini-extension)<a href="https://agentmods.dev/plugins/hostinger/api-mcp-server/gemini-extension"><img src="https://agentmods.dev/badge/plugins/hostinger/api-mcp-server/gemini-extension/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/hostinger/api-mcp-server/gemini-extension"><img src="https://agentmods.dev/badge/plugins/hostinger/api-mcp-server/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hostinger-api-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "hostinger-api-mcp",
"version": "3.22.3",
"description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
"mcpServers": {
"hostinger": {
"command": "npx",
"args": [
"-y",
"@hostinger/mcp"
],
"env": {
"HOSTINGER_API_TOKEN": "${HOSTINGER_API_TOKEN}"
}
}
},
"settings": [
{
"name": "Hostinger API Token",
"description": "Hostinger API token from hpanel.hostinger.com/profile/api. Optional — when unset, the server falls back to interactive OAuth sign-in in stdio mode.",
"envVar": "HOSTINGER_API_TOKEN",
"sensitive": true
}
]
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed 973f5ce0cca8
- yesterday Changed 8fda76cdd4ed
- 2d ago Changed 331957b4c77a
- 3d ago Changed ff0f0420a5f7
- 6d ago Changed 6cb0fc66595b
- 7d ago Changed 25344e2fe65e
- 8d ago Changed 3939c3da074d
- 9d ago Changed 541aa8989dc3
- 10d ago Changed b7147c23a598
- 13d ago First seen · 25 lines scan A 2834cd565e73
hostinger-api-mcp is a plugin published in the GitHub repository hostinger/api-mcp-server (165 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other plugins, from other repositories
database-cloud-optimization
Database query optimization, cloud cost optimization, and scalability improvements.
deployment-strategies
Deployment patterns, rollback automation, and infrastructure templates.
deployment-validation
Pre-deployment checks, configuration validation, and deployment readiness assessment.
gcloud-tools
Query Google Cloud logs, metrics, and traces through the Cloud Observability MCP.
porkbun
Manage the domains you own at Porkbun from Claude: DNS, nameservers, forwarding, DNSSEC, restore points and Secure Static Hosting, including publishing a site Claude builds for you.
mirrord
Connect your agent to a live Kubernetes cluster with mirrord, so it tests code changes against real services. Covers setup, config, CI, database branching, queue splitting, and preview environments.