Qsale MCP Server

qsale-mcp PyPI v0.2.1

Published by qsale-io — 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.

Model Context Protocol server for the QSale platform — catalog, content, segments, dictionaries, mailings, and admin tasks via console.qsale.io REST.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — 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 9

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([get_page]) co-exist with external-action tools ([propose_promotion_trigger_create]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_page] → sinks [propose_promotion_trigger_create]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow get_page → propose_promotion_trigger_create

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

Tool "propose_unlink_di_segment" can write, overwrite or delete files (keyword "unlink" 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 propose_unlink_di_segment

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

Tool "apply_unlink_di_segment" can write, overwrite or delete files (keyword "unlink" 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 apply_unlink_di_segment

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

Tool "propose_unlink_pc_segment" can write, overwrite or delete files (keyword "unlink" 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 propose_unlink_pc_segment

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

Tool "apply_unlink_pc_segment" can write, overwrite or delete files (keyword "unlink" 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 apply_unlink_pc_segment

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

Tool "propose_unlink_di_segment" 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 propose_unlink_di_segment

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

Tool "apply_unlink_di_segment" 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 apply_unlink_di_segment

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

Tool "propose_unlink_pc_segment" 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 propose_unlink_pc_segment

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

Tool "apply_unlink_pc_segment" 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 apply_unlink_pc_segment

Tools 110

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

  • apply_unlink_di_segmentwrites files
  • apply_unlink_pc_segmentwrites files
  • get_pageingests untrusted input
  • propose_promotion_trigger_createnetwork egress
  • propose_unlink_di_segmentwrites files
  • propose_unlink_pc_segmentwrites files
  • apply_category_createno sensitive capability
  • apply_category_deleteno sensitive capability
  • apply_dictionary_createno sensitive capability
  • apply_dictionary_deleteno sensitive capability
Show 100 more tools ↓
  • apply_dictionary_item_createno sensitive capability
  • apply_dictionary_item_deleteno sensitive capability
  • apply_link_di_segmentno sensitive capability
  • apply_link_pc_segmentno sensitive capability
  • apply_mail_template_createno sensitive capability
  • apply_mail_template_updateno sensitive capability
  • apply_navigation_item_createno sensitive capability
  • apply_navigation_item_updateno sensitive capability
  • apply_page_updateno sensitive capability
  • apply_promotion_createno sensitive capability
  • apply_promotion_prolongno sensitive capability
  • apply_promotion_trigger_createno sensitive capability
  • apply_promotion_updateno sensitive capability
  • apply_run_set_category_for_productsno sensitive capability
  • apply_run_update_all_dictsno sensitive capability
  • apply_run_update_dictno sensitive capability
  • apply_segment_createno sensitive capability
  • apply_segment_deleteno sensitive capability
  • apply_segment_filter_createno sensitive capability
  • apply_segment_filter_deleteno sensitive capability
  • apply_segment_filter_updateno sensitive capability
  • apply_segment_property_choice_createno sensitive capability
  • apply_segment_property_choice_deleteno sensitive capability
  • apply_segment_property_createno sensitive capability
  • apply_segment_property_deleteno sensitive capability
  • apply_segment_property_updateno sensitive capability
  • bulk_applyno sensitive capability
  • create_mail_template_imageno sensitive capability
  • create_redirectno sensitive capability
  • create_redirect_siteno sensitive capability
  • get_categoryno sensitive capability
  • get_dictionaryno sensitive capability
  • get_dictionary_itemno sensitive capability
  • get_frontend_settingno sensitive capability
  • get_mail_templateno sensitive capability
  • get_navigation_itemno sensitive capability
  • get_productno sensitive capability
  • get_promotionno sensitive capability
  • get_promotion_codeno sensitive capability
  • get_promotion_triggerno sensitive capability
  • get_segmentno sensitive capability
  • get_segment_filterno sensitive capability
  • get_segment_propertyno sensitive capability
  • list_categoriesno sensitive capability
  • list_di_segmentsno sensitive capability
  • list_dictionariesno sensitive capability
  • list_dictionary_itemsno sensitive capability
  • list_frontend_settingsno sensitive capability
  • list_mail_template_imagesno sensitive capability
  • list_mail_templatesno sensitive capability
  • list_navigation_groupsno sensitive capability
  • list_navigation_itemsno sensitive capability
  • list_pagesno sensitive capability
  • list_pc_segmentsno sensitive capability
  • list_productsno sensitive capability
  • list_promotion_codesno sensitive capability
  • list_promotion_triggersno sensitive capability
  • list_promotionsno sensitive capability
  • list_proposalsno sensitive capability
  • list_redirect_sitesno sensitive capability
  • list_redirectsno sensitive capability
  • list_segment_filtersno sensitive capability
  • list_segment_propertiesno sensitive capability
  • list_segment_property_choicesno sensitive capability
  • list_segmentsno sensitive capability
  • list_trigger_categoriesno sensitive capability
  • propose_category_createno sensitive capability
  • propose_category_deleteno sensitive capability
  • propose_dictionary_createno sensitive capability
  • propose_dictionary_deleteno sensitive capability
  • propose_dictionary_item_createno sensitive capability
  • propose_dictionary_item_deleteno sensitive capability
  • propose_link_di_segmentno sensitive capability
  • propose_link_pc_segmentno sensitive capability
  • propose_mail_template_createno sensitive capability
  • propose_mail_template_updateno sensitive capability
  • propose_navigation_item_createno sensitive capability
  • propose_navigation_item_updateno sensitive capability
  • propose_page_updateno sensitive capability
  • propose_promotion_createno sensitive capability
  • propose_promotion_prolongno sensitive capability
  • propose_promotion_updateno sensitive capability
  • propose_run_set_category_for_productsno sensitive capability
  • propose_run_update_all_dictsno sensitive capability
  • propose_run_update_dictno sensitive capability
  • propose_segment_createno sensitive capability
  • propose_segment_deleteno sensitive capability
  • propose_segment_filter_createno sensitive capability
  • propose_segment_filter_deleteno sensitive capability
  • propose_segment_filter_updateno sensitive capability
  • propose_segment_property_choice_createno sensitive capability
  • propose_segment_property_choice_deleteno sensitive capability
  • propose_segment_property_createno sensitive capability
  • propose_segment_property_deleteno sensitive capability
  • propose_segment_property_updateno sensitive capability
  • set_frontend_setting_fileno sensitive capability
  • update_categoryno sensitive capability
  • update_frontend_setting_jsonno sensitive capability
  • update_redirectno sensitive capability
  • update_redirect_siteno 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.2.1 latest A 96/100 9 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: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/qsale-mcp/badge.svg)](https://mcptrustchecker.com/registry/qsale-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/qsale-mcp"><img src="https://mcptrustchecker.com/registry/qsale-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/qsale-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 qsale-mcp --online --registry pypi

Use the free API → How scoring works

More in Business & CRM