@4ears-me/arcane-mcp
npm
v1.0.0
Published by @4ears-me — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for controlling Arcane Docker Management
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 12 = 88. 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:
| Points | Adoption-risk factor |
|---|---|
| −10 | capability blast radius (critical) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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.
This server (without client built-ins) exposes a complete data-exfiltration chain: arcane_browse_volume → arcane_get_environment → arcane_create_container. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow arcane_browse_volume → arcane_get_environment → arcane_create_container
Tool "arcane_create_container" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool arcane_create_container
Tool "arcane_create_container" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool arcane_create_container · inputSchema.properties.command
Tool "arcane_create_container" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool arcane_create_container
Each tool and what it can reach — statically extracted from the published source.
arcane_browse_volumeingests untrusted inputarcane_create_containerruns code / shellarcane_get_environmentreads sensitive dataarcane_create_environmentno sensitive capabilityarcane_create_networkno sensitive capabilityarcane_create_projectno sensitive capabilityarcane_create_volumeno sensitive capabilityarcane_create_volume_backupno sensitive capabilityarcane_delete_containerno sensitive capabilityarcane_delete_environmentno sensitive capabilityarcane_delete_projectno sensitive capabilityarcane_deploy_projectno sensitive capabilityarcane_get_containerno sensitive capabilityarcane_get_container_countsno sensitive capabilityarcane_get_docker_infono sensitive capabilityarcane_get_healthno sensitive capabilityarcane_get_imageno sensitive capabilityarcane_get_image_countsno sensitive capabilityarcane_get_networkno sensitive capabilityarcane_get_projectno sensitive capabilityarcane_get_project_countsno sensitive capabilityarcane_get_system_infono sensitive capabilityarcane_get_versionno sensitive capabilityarcane_get_volumeno sensitive capabilityarcane_get_volume_fileno sensitive capabilityarcane_get_volume_sizesno sensitive capabilityarcane_list_containersno sensitive capabilityarcane_list_environmentsno sensitive capabilityarcane_list_imagesno sensitive capabilityarcane_list_networksno sensitive capabilityarcane_list_projectsno sensitive capabilityarcane_list_volume_backupsno sensitive capabilityarcane_list_volumesno sensitive capabilityarcane_prune_imagesno sensitive capabilityarcane_prune_networksno sensitive capabilityarcane_prune_systemno sensitive capabilityarcane_prune_volumesno sensitive capabilityarcane_pull_imageno sensitive capabilityarcane_pull_project_imagesno sensitive capabilityarcane_redeploy_projectno sensitive capabilityarcane_remove_imageno sensitive capabilityarcane_remove_networkno sensitive capabilityarcane_remove_volumeno sensitive capabilityarcane_restart_containerno sensitive capabilityarcane_restart_projectno sensitive capabilityarcane_restore_volume_backupno sensitive capabilityarcane_start_containerno sensitive capabilityarcane_stop_containerno sensitive capabilityarcane_stop_projectno sensitive capabilityarcane_test_environmentno sensitive capabilityarcane_update_environmentno sensitive capabilityarcane_update_projectno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
B 88/100 | 4 | 1.13.0 | 2026-09-07 |
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.
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 @4ears-me/arcane-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
MCP Server for Arcane Docker Management API - Modern Docker Management for AI Assistants
MCP client for licensed Arcane content (thin stdio).
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.