Azure vs Hostinger API
These two are level on the tashan score (within 2 points), so the score does not decide it. The evidence rows below are where they differ. 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 ›
| Azure | Hostinger API | what it means | |
|---|---|---|---|
| tashan score | 86 | 88 | upkeep + freshness, gated by adoption |
| Adoption evidence | 107k/wk | 68k/wk | the raw public signal the score came from |
| Last release | active | active | npm publish or repo push |
| Upkeep | 99 | 99 | cadence, maintainers, status |
| Expertise grade | not graded | deep | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, runs an install script, no build provenance | no known advisories | a summary — the full audit, free, is on each dossier |
| Licence | MIT | MIT | |
| Maintainers | more than one | more than one | bus-factor risk |
Install either
Azure
claude mcp add azure -- npx -y @azure/mcpHostinger API
claude mcp add hostinger-api -- npx -y hostinger-api-mcpNeither 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: Azure · Hostinger API.
Both numbers above are today’s. Whichever you pick, the question that matters next is when it changes — and this page cannot know that. Pro keeps the series behind each capability, and names what to move to.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.