Skip to main content
Glama
leonhoulier

Infomaniak AI

by leonhoulier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Infomaniak AI

No user-submitted related servers found.

    Related Servers

    • enterprise-mcp

      dbett4
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.
      MIT

    • dot API shim

      rkz211
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables a private, owner-authenticated MCP client to call approved upstream APIs through a server-owned registry, with server-held credentials, fixed origins, bounded responses, and distinct read/write tools. Writes are opt-in and durably recorded with stable operation identifiers.
      MIT

    • Technitium DNS MCP

      X1pheR
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    status and read are clearly distinct (policy check vs. executing a reviewed read). search and catalogue both address API metadata discovery and could be confused, though the descriptions hint at different scopes (operation discovery vs. browsing by product/method).

    Naming Consistency5/5

    All four tools use the same infomaniak_ prefix with snake_case suffixes. The pattern is entirely predictable across the set.

    Tool Count4/5

    Four tools is reasonable for a discovery-plus-read server. Slightly thin, but each tool maps to a distinct capability (status, search, browse, execute read).

    Completeness3/5

    The surface is intentionally read-only with discovery, so no mutation/execution tools exist. This covers metadata lookup and reads but leaves a notable gap for any write workflow, which agents cannot work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources