io.github.leonhoulier/infomaniak-mcp
Infomaniak MCP (unofficial)
Is the Infomaniak MCP (unofficial) MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-30.
Manage Infomaniak DNS, mail and VPS apps through OAuth, with live official documentation.
needs auth probed 2026-11-15 · unchanged since 2026-10-30 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing Authorization header"}- Endpoint
- https://infomaniak-mcp.com/mcp (streamable-http)
- Host
- infomaniak-mcp.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://infomaniak-mcp.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server infomaniak-mcp.com, PKCE S256, grants authorization_code, refresh_token.
Scopes infomaniak:read infomaniak:write:disposable-dns infomaniak:write:dns infomaniak:write:mail infomaniak:deploy.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/leonhoulier/infomaniak-ai
- Website
- https://infomaniak-mcp.com
- Registry
- active, updated 2026-10-29 · registry entry
Compare this server with others.
More servers
Servers that mention infomaniak or unofficial.
- io.github.Mogacode-ma/infomaniak-mcp-agent · alive
- ai.smithery/keithah-tessie-mcp · not found
- LinkedIn Ads Library (unofficial) com.adpeekly/linkedin-ads-library · needs auth
- Gonkbot com.gonkbot/mcp · needs auth
- com.jojapi/reddit-com · alive
- Google Analytics (unofficial) com.safe-mcp/google-analytics-unofficial · alive
- com.scraptik/tiktok · alive
- io.capawesome/capacitor-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.