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 ecommercegit 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/ecommerce)<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/ecommerce"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/ecommerce/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/ecommerce"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/ecommerce.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.00070 | $0.02173 |
| Opus 5.5 | $0.00028 | $0.00869 |
| Sonnet 5.5 | $0.00014 | $0.00435 |
| Haiku 4.5 | $0.00007 | $0.00217 |
Grade A, and why
headless-step-provision-ecommerce 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
headless-step-provision-ecommerce
Provision a Hostinger Ecommerce backend for <domain> and prove it is ready. Two distinct things:
- A headless website (
type: "headless_ecommerce") — this is only the hosting slot for the storefront you'll build. It installs no store engine (no/cms, no API on the domain). - A Hostinger Ecommerce store — a separate object created through the Ecommerce API, with a custom (headless) sales channel. The storefront reads this store's public Storefront Core V2 API, keyed on the sales channel. This is the real backend.
Out: site.json (store id, custom sales channel id, URLs).
⚠️ Prerequisite: the
hostinger-ecommerceMCP server must be connectedStore management is not in the
hosting/wordpressMCP groups — it's the separatehostinger-ecommercegroup (ecommerce_*ops, OAuth-backed, no API token needed). If those tools aren't available, add the server and reconnect the session before continuing:claude mcp add-json hostinger-ecommerce '{"command":"npx","args":["--package=@hostinger/mcp@latest","hostinger-ecommerce-mcp"],"env":{"USER_AGENT":"extension;claude-code;via-cursor;1.4.2"}}' --scope user(For other tools, enable the Ecommerce MCP in the Hostinger Connector.) A newly added MCP server only loads on a session restart/reconnect.
Can't restart your own session? Don't block — drive the server directly. A coding agent usually can't reconnect itself, so instead of stopping, run the stdio server yourself and speak MCP to it: spawn
npx --package=@hostinger/mcp@latest hostinger-ecommerce-mcp(sameUSER_AGENTas above) and send newline-delimited JSON-RPC over its stdin/stdout —initialize→ thenotifications/initializednotification →tools/list→tools/call, where the tools aresearch/execute/multi-execute(call ops exactly as in-session:{ "name": "execute", "arguments": { "operation": "…", "params": {…} } }). It self-authenticates with the same stored Hostinger OAuth creds as the other connected servers, so there is no token to handle (keep any secret off the command line). Your sandbox may ask the user to approve spawning it — ask once, then proceed. Only fall back to asking the user to restart if driving the server directly isn't permitted.Verify the tools work (in-session or via the direct drive) with a search — e.g. "list stores" →
ecommerce_stores_list— before proceeding. The authoritative, always-current build guide isecommerce_miscellaneous_custom-storefront-setup-instructions— read it once per build.
All website-lifecycle calls go through the hosting connector (execute); all store calls through the
hostinger-ecommerce MCP.
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 First seen · 143 lines · 70 tokens per session scan A b842b52f568c
headless-step-provision-ecommerce is a skill published in the GitHub repository hostinger/api-mcp-server (163 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 2,173 once invoked, about $0.0003 per session on Opus 5.5. 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-10-20.
Other skills, from other repositories
odoo-docker-deployment
Production-ready Docker and docker-compose setup for Odoo with PostgreSQL, persistent volumes, environment-based configuration, and Nginx reverse proxy.
tray-cupons
API completa de cupons de desconto da Tray (recurso discountcoupons). Cobre criar, editar, listar, consultar e excluir cupons (CRUD) e gerenciar os relacionamentos do cupom com clientes, produtos, categorias, marcas, fretes e cupom-presente, além da geração de cupom de troca a partir de um pedido. Total de 21…
tray-status-pedido
API de Status de Pedido da Tray (recurso /orders/statuses). Cobre o CRUD completo do CATÁLOGO de status de pedido da loja: listar, consultar por ID, criar, atualizar e excluir tipos de status, definindo nome, descrição, cores hexadecimais (backgroundcolor/fontcolor) e o tipo de fluxo (type: open/closed/cancelled).…
tray-multicd
API de Multi-CD (Centros de Distribuição) da Tray. Cobre o CRUD de centros de distribuição (/multicd/distribution-centers: listar, consultar, criar, atualizar e excluir CDs) e a gestão de estoque distribuído por CD (/multicd/stock/detailed/product/:id, /multicd/stock/detailed/variant/:id e PUT…
tray-pagamentos
API de informações de pagamento da Tray (recurso payments). Cobre listar, consultar, criar, atualizar e excluir registros de pagamento (CRUD em /payments), além de consultar as opções de pagamento ativas da loja (/payments/options) e as configurações globais de pagamento (/payments/settings). Total de 7 endpoints.…
tray-configuracao-frete
API de Configuração de Frete da Tray. Utilize quando o desenvolvedor precisar gerenciar métodos de envio e tabelas de faixa de CEP da loja, incluindo criação, atualização e exclusão de formas de envio e suas respectivas tabelas de CEP com faixas de peso, preços e prazos. Essencial para configurar regras de frete…