Stigmer vs Hostinger API MCP
A side-by-side look at the Stigmer and Hostinger API MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Stigmer for cloud platforms work over a hosted endpoint; choose Hostinger API MCP for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Stigmer when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
query, list_services, list_methods.
Choose Hostinger API MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
HOSTINGER_API_TOKEN, API_TOKEN, OAUTH_ISSUER, DEBUG. - You want tools like
search, execute, multi-execute.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 55/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | HOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUERDEBUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 164 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | 3 |
| Full listing | View Stigmer | View Hostinger API MCP |
Tools & capabilities
Stigmer tools 8
querySearch for verified method contracts for any library. Pass any text -- library name, method, what you're building, or an error you hit.list_servicesList all libraries and services that have verified method contracts. Use this first to discover what's available, then query for specific methods.list_methodsList all methods for a given library or service. Use after list_services to drill into a specific one.policyGenerate a least-privilege IAM policy for an AWS workflow. Pass a named workflow, explicit IAM actions, or a description. Returns the exact policy with confidence tier and any unresolved operations.list_workflowsList the curated named workflows that can generate least-privilege IAM policies.verifyFeed a generated policy back to AWS's own policy evaluation engine (SimulateCustomPolicy) and confirm it grants exactly the intended operations and nothing extra. Returns verified (True|False|unknown), grants_all, grants_extra. Requires AWS credentials; without them verified=unknown with the reason. Wildcarded operations are expanded to concrete actions first.authorizePre-flight authorization check for an AWS operation. Resolves the IAM actions the operation requires, then asks AWS's own policy simulator (SimulatePrincipalPolicy) whether the current role (or a given principal) allows them. Returns resolution (exact|partial|unresolved) and evaluation (allowed|denied|unknown) as separate fields. Requires AWS credentials; without them evaluation=unknown with the reason.registerRegister a fix. Three actions: confirm (it worked), append_thread (variant worked), new_receipt (nothing matched, I fixed it).
Hostinger API MCP tools 3
searchfind operations by keyword; returns each match with its `inputSchema`.executerun one operation: `{ "operation": "<name>", "params": { ... } }`.multi-executerun up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Stigmer
{
"mcpServers": {
"stigmer": {
"url": "https://stigmer.network/mcp"
}
}
}
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"url": "https://mcp.hostinger.com"
}
}
}
Frequently asked questions
Stigmer is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Hostinger API MCP belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Stigmer for cloud platforms work and Hostinger API MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Stigmer has no declared pricing — check the project's own site. Hostinger API MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add stigmer and hostinger-api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stigmer has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Hostinger API MCP has 57/100 (Good) with 1 views, 0 installs and 164 GitHub stars.