@catalystdev/exteragram-mcp
npm
v1.0.0
Published by @catalystdev — 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.
MCP-сервер для разработки плагинов exteraGram — генерация Python-кода, справочники, деплой через ADB
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 − 7 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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.
Tools that read sensitive data ([adb_get_logs, generate_read_file]) and tools that can send data out ([adb_shell, generate_send_message, generate_send_message_hook]) are exposed together. An agent can move private data to the sink.
Evidence: sources [adb_get_logs, generate_read_file] → sinks [adb_shell, generate_send_message, generate_send_message_hook]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow adb_get_logs → adb_shell
Tool "adb_shell" appears to run shell commands or evaluate code (keyword "shell" in tool name, 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 adb_shell
In the server's implementation (`dist/tools/adb.js:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: port { execSync } from "child_process"; import { z } from "zod"; import { getPluginContext } from "../state/plugin-conte
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/adb.js
Tool "generate_write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool generate_write_file
Tool "generate_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool generate_delete_file
Tool "adb_shell" 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 adb_shell · inputSchema.properties.command
Tool "adb_shell" 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 adb_shell
Tool "generate_write_file" 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 generate_write_file
Tool "generate_delete_file" 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 generate_delete_file
Tool "generate_read_file" takes a path parameter "path_expr" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool generate_read_file · inputSchema.properties.path_expr
Tool "generate_write_file" takes a path parameter "path_expr" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool generate_write_file · inputSchema.properties.path_expr
Tool "generate_write_file" takes a path parameter "ensure_dir" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool generate_write_file · inputSchema.properties.ensure_dir
Tool "generate_delete_file" takes a path parameter "path_expr" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool generate_delete_file · inputSchema.properties.path_expr
Each tool and what it can reach — statically extracted from the published source.
adb_get_logsreads sensitive dataadb_shellruns code / shellgenerate_delete_filewrites filesgenerate_read_filereads sensitive datagenerate_send_messagenetwork egressgenerate_send_message_hooknetwork egressgenerate_write_filewrites filesadb_check_devicesno sensitive capabilityadb_deploy_pluginno sensitive capabilityadb_list_pluginsno sensitive capabilityadb_pull_fileno sensitive capabilityadb_push_fileno sensitive capabilityadb_remove_pluginno sensitive capabilityadb_restart_appno sensitive capabilityclear_plugin_contextno sensitive capabilityexplain_pitfallsno sensitive capabilitygenerate_alert_dialogno sensitive capabilitygenerate_bulletinno sensitive capabilitygenerate_click_listenerno sensitive capabilitygenerate_clipboard_copyno sensitive capabilitygenerate_edit_messageno sensitive capabilitygenerate_ensure_dirno sensitive capabilitygenerate_export_import_settingsno sensitive capabilitygenerate_find_classno sensitive capabilitygenerate_from_javano sensitive capabilitygenerate_get_fieldno sensitive capabilitygenerate_get_settingno sensitive capabilitygenerate_hook_all_constructorsno sensitive capabilitygenerate_hook_all_methodsno sensitive capabilitygenerate_hook_filtersno sensitive capabilitygenerate_hook_param_usageno sensitive capabilitygenerate_hook_resultno sensitive capabilitygenerate_import_blockno sensitive capabilitygenerate_java_helperno sensitive capabilitygenerate_java_subclassno sensitive capabilitygenerate_jclassbuilderno sensitive capabilitygenerate_jfieldno sensitive capabilitygenerate_jmvel_methodno sensitive capabilitygenerate_joverrideno sensitive capabilitygenerate_list_dirno sensitive capabilitygenerate_logno sensitive capabilitygenerate_menu_itemno sensitive capabilitygenerate_metadata_blockno sensitive capabilitygenerate_method_hookno sensitive capabilitygenerate_new_instanceno sensitive capabilitygenerate_notification_listenerno sensitive capabilitygenerate_on_app_eventno sensitive capabilitygenerate_on_plugin_loadno sensitive capabilitygenerate_on_plugin_unloadno sensitive capabilitygenerate_on_update_hookno sensitive capabilitygenerate_on_updates_hookno sensitive capabilitygenerate_parse_textno sensitive capabilitygenerate_plugin_fileno sensitive capabilitygenerate_post_request_hookno sensitive capabilitygenerate_pre_request_hookno sensitive capabilitygenerate_pyobjno sensitive capabilitygenerate_queue_callno sensitive capabilitygenerate_runnableno sensitive capabilitygenerate_send_requestno sensitive capabilitygenerate_set_fieldno sensitive capabilitygenerate_set_settingno sensitive capabilitygenerate_settings_componentno sensitive capabilitygenerate_settings_uino sensitive capabilitygenerate_simple_setting_factoryno sensitive capabilitygenerate_ui_thread_callno sensitive capabilitygenerate_unhookno sensitive capabilityget_plugin_contextno sensitive capabilityget_plugin_templateno sensitive capabilitylist_app_eventsno sensitive capabilitylist_available_librariesno sensitive capabilitylist_common_classesno sensitive capabilitylist_controllersno sensitive capabilitylist_hook_filtersno sensitive capabilitylist_hook_strategiesno sensitive capabilitylist_html_tagsno sensitive capabilitylist_menu_typesno sensitive capabilitylist_queue_constantsno sensitive capabilitylist_settings_componentsno sensitive capabilitylist_standard_dirsno sensitive capabilityset_plugin_contextno sensitive capabilityvalidate_plugin_metadatano 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 |
A 93/100 | 13 | 1.13.0 | 2026-09-08 |
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 @catalystdev/exteragram-mcp --online
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.