Infomaniak Mcp Agent MCP Server

infomaniak-mcp-agent npm v0.15.1

Published by mogacode-ma — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Full unofficial agentic Infomaniak MCP server — guided automation of web hosting, mail, kDrive, domains and DNS

Trust grade
F
56/100
Last scanned get badge →
Trust
F · 56/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
F Why this grade threat 67 − adoption risk = 56/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 32.7 = 67. What the published surface and source actually contain:

PointsWhat was foundCategory
−31.5 Self-contained exfiltration primitive: "infomaniak_nodejs_app_logs" MTC-FLOW-001 exfiltration
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 67 − 11 = 56. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Grade capped: a critical finding is present → grade capped at D. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

critical Self-contained exfiltration primitive: "infomaniak_nodejs_app_logs"MTC-FLOW-001

Tool "infomaniak_nodejs_app_logs" holds all three trifecta roles by itself (untrusted-input + sensitive-source + external-sink). A single call can pull attacker-controlled content, read private data, and exfiltrate it — no composition required.

Fix: Split responsibilities across separate, individually-consented tools; never combine untrusted input, secret reads, and egress in one tool.

Location: flow infomaniak_nodejs_app_logs

low Package runs install-time scripts (postinstall)MTC-SUP-010

"infomaniak-mcp-agent" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node scripts/postinstall.cjs || true

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package infomaniak-mcp-agent

Tools 78

Each tool and what it can reach — statically extracted from the published source.

  • infomaniak_nodejs_app_logsingests untrusted inputreads sensitive datanetwork egress
  • infomaniak_get_database_useringests untrusted input
  • infomaniak_list_drive_filesreads sensitive data
  • infomaniak_add_site_aliasesno sensitive capability
  • infomaniak_api_callno sensitive capability
  • infomaniak_audit_accountno sensitive capability
  • infomaniak_audit_dns_zonesno sensitive capability
  • infomaniak_change_database_user_passwordno sensitive capability
  • infomaniak_change_database_user_permissionsno sensitive capability
  • infomaniak_change_hosting_user_connection_typeno sensitive capability
Show 68 more tools ↓
  • infomaniak_change_hosting_user_passwordno sensitive capability
  • infomaniak_create_databaseno sensitive capability
  • infomaniak_create_hosting_userno sensitive capability
  • infomaniak_create_mailboxno sensitive capability
  • infomaniak_create_mailbox_aliasno sensitive capability
  • infomaniak_create_redirectionno sensitive capability
  • infomaniak_create_short_urlno sensitive capability
  • infomaniak_create_siteno sensitive capability
  • infomaniak_delete_certificateno sensitive capability
  • infomaniak_delete_databaseno sensitive capability
  • infomaniak_delete_hosting_userno sensitive capability
  • infomaniak_delete_mailboxno sensitive capability
  • infomaniak_delete_redirectionno sensitive capability
  • infomaniak_delete_siteno sensitive capability
  • infomaniak_delete_site_aliasno sensitive capability
  • infomaniak_dns_create_recordno sensitive capability
  • infomaniak_dns_delete_recordno sensitive capability
  • infomaniak_dns_list_recordsno sensitive capability
  • infomaniak_dns_update_recordno sensitive capability
  • infomaniak_explainno sensitive capability
  • infomaniak_find_siteno sensitive capability
  • infomaniak_get_account_fullno sensitive capability
  • infomaniak_get_certificateno sensitive capability
  • infomaniak_get_databaseno sensitive capability
  • infomaniak_get_domainno sensitive capability
  • infomaniak_get_domain_fullno sensitive capability
  • infomaniak_get_drive_fullno sensitive capability
  • infomaniak_get_mail_hosting_fullno sensitive capability
  • infomaniak_get_mailbox_fullno sensitive capability
  • infomaniak_get_mailbox_infono sensitive capability
  • infomaniak_get_my_profileno sensitive capability
  • infomaniak_get_my_securityno sensitive capability
  • infomaniak_get_nodejs_appno sensitive capability
  • infomaniak_get_vps_fullno sensitive capability
  • infomaniak_helpno sensitive capability
  • infomaniak_historyno sensitive capability
  • infomaniak_list_ai_modelsno sensitive capability
  • infomaniak_list_ai_productsno sensitive capability
  • infomaniak_list_database_usersno sensitive capability
  • infomaniak_list_databasesno sensitive capability
  • infomaniak_list_domainsno sensitive capability
  • infomaniak_list_drive_trashno sensitive capability
  • infomaniak_list_drive_usersno sensitive capability
  • infomaniak_list_drivesno sensitive capability
  • infomaniak_list_hosting_usersno sensitive capability
  • infomaniak_list_hostingsno sensitive capability
  • infomaniak_list_mail_hostingsno sensitive capability
  • infomaniak_list_mailboxesno sensitive capability
  • infomaniak_list_nodejs_appsno sensitive capability
  • infomaniak_list_organizationsno sensitive capability
  • infomaniak_list_redirectionsno sensitive capability
  • infomaniak_list_short_urlsno sensitive capability
  • infomaniak_list_site_aliasesno sensitive capability
  • infomaniak_list_sitesno sensitive capability
  • infomaniak_list_swiss_backupsno sensitive capability
  • infomaniak_list_teams_and_tagsno sensitive capability
  • infomaniak_list_vpsno sensitive capability
  • infomaniak_manage_dnssecno sensitive capability
  • infomaniak_nodejs_app_actionno sensitive capability
  • infomaniak_nodejs_app_aliasesno sensitive capability
  • infomaniak_nodejs_app_jobsno sensitive capability
  • infomaniak_nodejs_app_statusno sensitive capability
  • infomaniak_nodejs_app_thumbnailno sensitive capability
  • infomaniak_overviewno sensitive capability
  • infomaniak_provision_site_fullno sensitive capability
  • infomaniak_request_certificateno sensitive capability
  • infomaniak_short_urls_quotano sensitive capability
  • infomaniak_undono sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.15.1 latest F 56/100 2 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: F · 56/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/infomaniak-mcp-agent/badge.svg)](https://mcptrustchecker.com/registry/infomaniak-mcp-agent)
HTML
<a href="https://mcptrustchecker.com/registry/infomaniak-mcp-agent"><img src="https://mcptrustchecker.com/registry/infomaniak-mcp-agent/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/infomaniak-mcp-agent/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan infomaniak-mcp-agent --online

Use the free API → How scoring works

More in AI & Agents