audit-hosting
Audit a Hostinger web hosting account (Shared, Cloud and Agency plans) and report what needs attention: every plan and website, SSL problems, broken or vulnerable WordPress installs, failed Node.js builds and vulnerable npm packages, databases and Agency Plan orders near their limits, and hosting plans about to lapse. Read-only; produces a prioritised to-do list and names the skill that fixes each item. Triggers: what do I have on Hostinger, audit my hosting, check all my websites, what needs attention, health check my sites, are any of my sites broken, which of my sites are insecure.
How do I install this agent skill?
npx skills add https://github.com/hostinger/api-mcp-server --skill audit-hostingIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill performs a comprehensive security and health audit of Hostinger hosting accounts. It queries official APIs to check for vulnerabilities, SSL status, and resource usage, providing a prioritized report for the user.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Audit hosting
Read-only from start to finish. The output is a report; every fix is a separate, confirmed step through another skill.
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. "ssl status"). - Batch reads with
multi-execute, up to 20 steps a batch. Batches chain operations from one server only — the Hostinger Connector runshosting,wordpress,agency-hostingandbillingas separate servers. When a product group is switched off, skip its checks and say which were skipped. - Page every list until
meta.totalis covered. - Leave
hosting_php_getout — it is large and says nothing about account health.
1. Inventory
One batch per server:
hosting_orders_listwithstatuses: ["active", "suspended"].cloud_*plan names are Cloud; the rest (hostinger_premium_*,hostinger_business_*, …) are Shared.hosting_websites_list— every Shared and Cloud website withwebsite_type,username,order_idandis_enabled(false means suspended).wordpress_installations_listwithownership: "all"—id,is_valid,validation_error.agency-hosting_orders_listandagency-hosting_websites_list-plan— Agency orders and sites (details.uid,details.type,details.domains,details.state).
Tell the user the size (plans, websites, WordPress installs) before the checks. For large accounts offer to scope the audit to one order or domain.
2. Checks
Per Shared and Cloud website (skip builder and horizons):
hosting_websites_get-settings— inssl, flagfailed(withlast_error),expired,not_installedon a custom domain,is_https_redirect_enabled: false, andexpires_atwithin 30 days whenis_lifetimeis false; lifetime certificates renew on their own. Incache, flagis_cacheless_mode_enabled: true(development mode left on) andis_enabled: false.- Node.js sites:
hosting_get-deployment(latest build failed?build.state) andhosting_nodejs_list-vulnerabilitieswithseverities: ["critical", "high"].
Per hosting account (username): hosting_databases_list — flag disk_usage_mb above 80% of max_size_mb.
Per WordPress install: wordpress_installations_show-core-version (core vulnerabilities) and wordpress_plugins_list-installed (vulnerable plugins and pending updates).
Per Agency order: agency-hosting_metrics_list-order-resource-usage with time_frame_hours: 168 and agency-hosting_metrics_list-plan-order-disk-usage with time_frame_days: 7 — flag usage above 80% of the plan quota and name the heaviest websites.
Per Agency site: agency-hosting_ssl_website-status for each custom domain in details.domains; flag details.state other than active.
Plans about to lapse (billing product): billing_subscriptions_list, joined to hosting orders on subscription_id — flag not_renewing, or is_auto_renewed: false with expires_at within 30 days. Every site on that plan goes down with it.
From outside, for each custom domain:
curl -sS -o /dev/null -w "%{http_code}\n" --max-time 15 https://DOMAIN/
curl -sSI --max-time 15 https://DOMAIN/ | grep -i "^platform"
No platform: hostinger header means the domain does not reach this hosting.
3. Report
# Hosting audit
3 plans (2 Shared, 1 Cloud) + 1 Agency · 14 websites (6 WordPress, 3 Node.js, 5 other) · 4 Agency sites
## Fix now
- shop.example.com — latest Node.js build failed 2 days ago → troubleshoot-website
- blog.example.com — contact-form-x 5.2 has a known vulnerability, fixed in 5.3 → maintain-wordpress
## Soon
- example.org — Business plan expires in 12 days, auto-renew off → renew in hPanel
- Agency order 1000000001 — 86% of disk quota, mostly client-a.com
## Worth knowing
- 4 WordPress installs have pending plugin updates → maintain-wordpress
## Healthy
docs.example.com, portfolio.example.com, …
- Fix now: site down or not reaching Hostinger, failed latest build, invalid WordPress install, SSL
failedorexpired, critical vulnerabilities, suspended website. - Soon: high vulnerabilities, a plan lapsing within 30 days, usage above 80% of a quota, HTTPS redirect off, non-lifetime certificates expiring.
- Worth knowing: pending updates, inactive plugins with vulnerabilities.
Each item names the evidence and the skill that fixes it: troubleshoot-website, maintain-wordpress, connect-domain or deploy-to-hosting. Patchable npm vulnerabilities on GitHub-deployed sites can be fixed with hosting_nodejs_patch-vulnerabilities, which opens a pull request — offer it, do not run it as part of the audit.
Not available through the API
CPU and memory usage for Shared and Cloud plans, website backup status, and PHP error logs. Mention them once at the end so the user knows what the audit could not see.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/hostinger/api-mcp-server/audit-hosting">View audit-hosting on skillZs</a>