Exteragram MCP Server

@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

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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
A Why this grade threat 100 − adoption risk = 93/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 − 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:

PointsAdoption-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.

Findings 13

high Sensitive-source and external-sink co-existMTC-FLOW-004

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

high Tool "adb_shell" exposes command/code executionMTC-CAP-001

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

high Shell/command execution in server code (dist/tools/adb.js)MTC-SRC-002

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

medium Tool "generate_write_file" can modify the filesystemMTC-CAP-002

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

medium Tool "generate_delete_file" can modify the filesystemMTC-CAP-002

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

medium Unconstrained command parameter "command" on "adb_shell"MTC-CAP-006

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

low Mutating tool "adb_shell" declares no destructiveHintMTC-CAP-005

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

low Mutating tool "generate_write_file" declares no destructiveHintMTC-CAP-005

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

low Mutating tool "generate_delete_file" declares no destructiveHintMTC-CAP-005

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

low Unconstrained path parameter "path_expr" on "generate_read_file"MTC-CAP-008

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

low Unconstrained path parameter "path_expr" on "generate_write_file"MTC-CAP-008

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

low Unconstrained path parameter "ensure_dir" on "generate_write_file"MTC-CAP-008

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

low Unconstrained path parameter "path_expr" on "generate_delete_file"MTC-CAP-008

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

Tools 81

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

  • adb_get_logsreads sensitive data
  • adb_shellruns code / shell
  • generate_delete_filewrites files
  • generate_read_filereads sensitive data
  • generate_send_messagenetwork egress
  • generate_send_message_hooknetwork egress
  • generate_write_filewrites files
  • adb_check_devicesno sensitive capability
  • adb_deploy_pluginno sensitive capability
  • adb_list_pluginsno sensitive capability
Show 71 more tools ↓
  • adb_pull_fileno sensitive capability
  • adb_push_fileno sensitive capability
  • adb_remove_pluginno sensitive capability
  • adb_restart_appno sensitive capability
  • clear_plugin_contextno sensitive capability
  • explain_pitfallsno sensitive capability
  • generate_alert_dialogno sensitive capability
  • generate_bulletinno sensitive capability
  • generate_click_listenerno sensitive capability
  • generate_clipboard_copyno sensitive capability
  • generate_edit_messageno sensitive capability
  • generate_ensure_dirno sensitive capability
  • generate_export_import_settingsno sensitive capability
  • generate_find_classno sensitive capability
  • generate_from_javano sensitive capability
  • generate_get_fieldno sensitive capability
  • generate_get_settingno sensitive capability
  • generate_hook_all_constructorsno sensitive capability
  • generate_hook_all_methodsno sensitive capability
  • generate_hook_filtersno sensitive capability
  • generate_hook_param_usageno sensitive capability
  • generate_hook_resultno sensitive capability
  • generate_import_blockno sensitive capability
  • generate_java_helperno sensitive capability
  • generate_java_subclassno sensitive capability
  • generate_jclassbuilderno sensitive capability
  • generate_jfieldno sensitive capability
  • generate_jmvel_methodno sensitive capability
  • generate_joverrideno sensitive capability
  • generate_list_dirno sensitive capability
  • generate_logno sensitive capability
  • generate_menu_itemno sensitive capability
  • generate_metadata_blockno sensitive capability
  • generate_method_hookno sensitive capability
  • generate_new_instanceno sensitive capability
  • generate_notification_listenerno sensitive capability
  • generate_on_app_eventno sensitive capability
  • generate_on_plugin_loadno sensitive capability
  • generate_on_plugin_unloadno sensitive capability
  • generate_on_update_hookno sensitive capability
  • generate_on_updates_hookno sensitive capability
  • generate_parse_textno sensitive capability
  • generate_plugin_fileno sensitive capability
  • generate_post_request_hookno sensitive capability
  • generate_pre_request_hookno sensitive capability
  • generate_pyobjno sensitive capability
  • generate_queue_callno sensitive capability
  • generate_runnableno sensitive capability
  • generate_send_requestno sensitive capability
  • generate_set_fieldno sensitive capability
  • generate_set_settingno sensitive capability
  • generate_settings_componentno sensitive capability
  • generate_settings_uino sensitive capability
  • generate_simple_setting_factoryno sensitive capability
  • generate_ui_thread_callno sensitive capability
  • generate_unhookno sensitive capability
  • get_plugin_contextno sensitive capability
  • get_plugin_templateno sensitive capability
  • list_app_eventsno sensitive capability
  • list_available_librariesno sensitive capability
  • list_common_classesno sensitive capability
  • list_controllersno sensitive capability
  • list_hook_filtersno sensitive capability
  • list_hook_strategiesno sensitive capability
  • list_html_tagsno sensitive capability
  • list_menu_typesno sensitive capability
  • list_queue_constantsno sensitive capability
  • list_settings_componentsno sensitive capability
  • list_standard_dirsno sensitive capability
  • set_plugin_contextno sensitive capability
  • validate_plugin_metadatano 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
v1.0.0 latest A 93/100 13 1.13.0 2026-09-08

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: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/catalystdev-exteragram-mcp/badge.svg)](https://mcptrustchecker.com/registry/catalystdev-exteragram-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/catalystdev-exteragram-mcp"><img src="https://mcptrustchecker.com/registry/catalystdev-exteragram-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/catalystdev-exteragram-mcp/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 @catalystdev/exteragram-mcp --online

Use the free API → How scoring works

More in Developer Tools