Hostinger API vs Modelcontextprotocol · @modelcontextprotocol
Hostinger API scores 4 points higher — a narrow lead. Read the evidence rows below before treating it as decisive. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| Hostinger API | Modelcontextprotocol · @modelcontextprotocol | what it means | |
|---|---|---|---|
| tashan score | 88 | 84 | upkeep + freshness, gated by adoption |
| Adoption evidence | 63k/wk | 458k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 99 | 91 | cadence, maintainers, status |
| Expertise grade | not graded | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories | no known advisories, no build provenance | a summary — the full audit, free, is on each dossier |
| Licence | MIT | — | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Hostinger API
claude mcp add hostinger-api -- npx -y hostinger-api-mcpModelcontextprotocol · @modelcontextprotocol
claude mcp add modelcontextprotocol-core -- npx -y @modelcontextprotocol/coreNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: Hostinger API · Modelcontextprotocol · @modelcontextprotocol.