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.
npx skills add hostinger/api-mcp-server --skill connect-domaingit 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/skills/hostinger/api-mcp-server/connect-domain)<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/connect-domain"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/connect-domain/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/skills/hostinger/api-mcp-server/connect-domain"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/connect-domain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00135 | $0.01661 |
| Opus 5.5 | $0.00054 | $0.00664 |
| Sonnet 5.5 | $0.00027 | $0.00332 |
| Haiku 4.5 | $0.00014 | $0.00166 |
Grade A, and why
connect-domain scanned grade A with 1 finding 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 16d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSI https://DOMAIN/ | grep -i -E "^(HTTP|platform|location)" How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect a domain
Get a domain serving a Hostinger website over HTTPS. The one rule that matters most: records that already work — email (MX), SPF, DKIM and verification TXT records — must survive every DNS change.
Calling the operations
- Read the
inputSchemathatsearchreturns before the first call of each operation. If a name below is rejected as unknown,searchfor what the step does (e.g. "dns records"). - Batch reads with
multi-execute; values pass between steps as$steps.<i>.<path>. Batches chain operations from one server only — the Hostinger Connector runshosting,agency-hosting,domainsanddnsas separate servers. Whensearchcannot find an operation, ask the user to enable that product group in the Connector. - Every write here changes what the public sees. State the change and get a yes before each one.
1. Gather the facts (read-only)
- Website.
hosting_websites_listwithdomain(Shared and Cloud; substring match, so take the exact entry) andagency-hosting_websites_list-planwithdomain(Agency). Keepusernameandorder_id, ordetails.uidanddetails.ipv4. When the domain has no website yet, find the site the user means — often a*.hostingersite.comone — or the order to create it on (hosting_orders_list,agency-hosting_orders_list). - Registration.
domains_portfolio_getsucceeds only for domains registered at Hostinger; itsname_serversshow who runs DNS. Hostinger's own nameservers end indns-parking.com. - Live DNS, to know what must be kept:
dig +short NS DOMAIN; dig +short A DOMAIN; dig +short CNAME www.DOMAIN
dig +short MX DOMAIN; dig +short TXT DOMAIN; dig +short CAA DOMAIN
2. Attach the domain to hosting
Shared and Cloud:
- New website on the domain. For a domain outside this account run
hosting_domains_verify-ownershipfirst. Whenis_accessibleis false, give the user theTXTrecord it returns to add next to the existing ones, then verify again (propagation takes up to ~10 minutes). Create withhosting_websites_create(domainwithoutwww.,order_id), then pollhosting_websites_list-setupswithdomainevery 10–15 s untilstatus: completed. - Moving a site off its free subdomain. Shared and Cloud websites cannot be renamed through the API. Either create a website on the real domain and redeploy the project there (the
deploy-to-hostingskill) — required for WordPress, which keeps its URL in the database — or, for static sites, park the domain on the existing site withhosting_domains_create-website-parked. - Alias (a second domain showing the same site):
hosting_domains_create-website-parked. - Subdomain (
shop.example.com):hosting_domains_create-website-subdomain.wwwbelongs to the main domain — do not create it as a subdomain.
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.
- 16d ago First seen · 70 lines · 135 tokens per session scan A cba4378a8f69
connect-domain is a skill published in the GitHub repository hostinger/api-mcp-server (163 stars, last pushed yesterday), licensed MIT. It adds 135 tokens to every session and 1,661 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-operator
Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…
mirrord-up
Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.