Sapo Omni MCP Server

sapo-omni-mcp npm v0.2.1

Published by minhquy3101 — 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 Server cho phép Claude AI tương tác với SAPO platform — quản lý sản phẩm, đơn hàng, khách hàng, kho hàng và khuyến mãi

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 51

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

  • adjust_inventoryno sensitive capability
  • archive_orderno sensitive capability
  • cancel_orderno sensitive capability
  • connect_inventory_itemno sensitive capability
  • count_customersno sensitive capability
  • count_ordersno sensitive capability
  • count_price_rulesno sensitive capability
  • count_productsno sensitive capability
  • create_customerno sensitive capability
  • create_discount_codeno sensitive capability
Show 41 more tools ↓
  • create_orderno sensitive capability
  • create_price_ruleno sensitive capability
  • create_productno sensitive capability
  • create_refundno sensitive capability
  • delete_customerno sensitive capability
  • delete_discount_codeno sensitive capability
  • delete_orderno sensitive capability
  • delete_price_ruleno sensitive capability
  • delete_productno sensitive capability
  • fulfill_orderno sensitive capability
  • get_carrier_serviceno sensitive capability
  • get_customerno sensitive capability
  • get_inventory_itemno sensitive capability
  • get_locationno sensitive capability
  • get_orderno sensitive capability
  • get_price_ruleno sensitive capability
  • get_productno sensitive capability
  • get_storeno sensitive capability
  • list_carrier_servicesno sensitive capability
  • list_customersno sensitive capability
  • list_discount_codesno sensitive capability
  • list_inventory_levelsno sensitive capability
  • list_locationsno sensitive capability
  • list_ordersno sensitive capability
  • list_price_rulesno sensitive capability
  • list_productsno sensitive capability
  • list_refundsno sensitive capability
  • list_transactionsno sensitive capability
  • order_status_summaryno sensitive capability
  • revenue_summaryno sensitive capability
  • search_products_by_skuno sensitive capability
  • set_inventory_levelno sensitive capability
  • set_inventory_levels_multino sensitive capability
  • top_products_by_revenueno sensitive capability
  • unarchive_orderno sensitive capability
  • update_customerno sensitive capability
  • update_discount_codeno sensitive capability
  • update_inventory_itemno sensitive capability
  • update_orderno sensitive capability
  • update_price_ruleno sensitive capability
  • update_productno sensitive capability

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 99/100 0 1.13.0 2026-09-07

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

Use the free API → How scoring works

More in Business & CRM