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/idugeni/hostinger-mcpWrote 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/mcp/idugeni/hostinger-mcp/hostinger-mcp-server)<a href="https://agentmods.dev/mcp/idugeni/hostinger-mcp/hostinger-mcp-server"><img src="https://agentmods.dev/badge/mcp/idugeni/hostinger-mcp/hostinger-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hostinger-mcp-server 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 7d ago.
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
{ "hostinger-mcp-server": { "command": "npx", "args": [ "-y", "hostinger-mcp-server" ] } }
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.
- 7d ago First seen · 9 lines scan A 7d88c0e94b72
hostinger-mcp-server is an MCP server published in the GitHub repository idugeni/hostinger-mcp (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-08-31.
Other mcp servers, from other repositories
globodai-mcp-gandi
MCP server "globodai-mcp-gandi" as configured in globodai-group/mcp-gandi. Runs locally from the globodai-mcp-gandi npm package.
globodai-mcp-gcloud-dns
MCP server "globodai-mcp-gcloud-dns" as configured in globodai-group/mcp-gcloud-dns. Runs locally from the globodai-mcp-gcloud-dns npm package.
globodai-mcp-cloudflare-dns
MCP server "globodai-mcp-cloudflare-dns" as configured in globodai-group/mcp-cloudflare-dns. Runs locally from the globodai-mcp-cloudflare-dns npm package.
defang
MCP server "defang" as configured in DefangLabs/defang. Launched with defang mcp serve.
cloudflare-mcp-pro
Cloudflare MCP: DNS, Zones, Workers, KV, R2, D1, Pages, WAF, SSL, Email, AI via REST API v4. Runs locally from the cloudflare-mcp-pro npm package. Needs 3 environment variables to run.
cloudflare
MCP server to manage Cloudflare Workers, KV, R2, Pages, DNS, and cache from your IDE. Runs locally from the mcp-server-cloudflare-dns npm package.