Make the hosted OAuth server discoverable from package/registry descriptions #75

The README leads with the hosted server (https://mcp.hostinger.com, OAuth), and the MCP Registry entry lists it under remotes. But the short descriptions, which are often the only thing a user, catalog or AI agent reads, don't mention it.

What happened

An AI coding assistant was asked to set up Hostinger MCP. It checked npm view hostinger-api-mcp, saw only "MCP server for Hostinger API", and recommended the stdio package with a manually generated API token. It never found out that hosted OAuth exists. The tool skipped the README, and that part is on the tool, but a one-line description would have prevented it.

Current state (checked 2026-10-10)

• npm hostinger-api-mcp 2.11.0: description MCP server for Hostinger API
• npm @hostinger/mcp 2.11.0: same description
• Registry io.github.hostinger/hostinger-api-mcp 2.11.0: same description. remotes and the optional HOSTINGER_API_TOKEN are correct.

Suggestions

1. Update description in package.json and server.json, for example:

   Manage Hostinger domains, hosting and VPS. Recommended: hosted server at https://mcp.hostinger.com (OAuth sign-in). This package runs locally over stdio.

2. State which npm name is canonical (@hostinger/mcp or hostinger-api-mcp) in the README and in both packages' descriptions. Right now two identical packages ship side by side, and older guides only mention the unscoped one.

Happy to open a PR for the description change if that helps.