Silpo MCP Server

silpo-mcp npm v2.0.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for the Silpo (Сільпо) online supermarket API — search products, browse categories, promotions, delivery zones/slots, carts and recipes via AI assistants.

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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 = 98/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 − 2 = 98. 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
−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.

Findings 0

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

Tools 37

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

  • add_item_commentno sensitive capability
  • add_to_cartno sensitive capability
  • add_to_shopping_listno sensitive capability
  • check_delivery_zoneno sensitive capability
  • clear_cartno sensitive capability
  • clear_shopping_listno sensitive capability
  • create_cartno sensitive capability
  • get_cartno sensitive capability
  • get_categoriesno sensitive capability
  • get_category_productsno sensitive capability
Show 27 more tools ↓
  • get_current_addressno sensitive capability
  • get_delivery_modesno sensitive capability
  • get_delivery_slotno sensitive capability
  • get_loyalty_balanceno sensitive capability
  • get_order_productsno sensitive capability
  • get_orders_historyno sensitive capability
  • get_productno sensitive capability
  • get_product_imagesno sensitive capability
  • get_promotionsno sensitive capability
  • get_recipe_filtersno sensitive capability
  • get_session_infono sensitive capability
  • get_shopping_listno sensitive capability
  • get_time_slotsno sensitive capability
  • remove_from_cartno sensitive capability
  • remove_from_shopping_listno sensitive capability
  • search_addressno sensitive capability
  • search_productsno sensitive capability
  • search_recipesno sensitive capability
  • set_auth_cookieno sensitive capability
  • set_auth_tokenno sensitive capability
  • set_basket_idno sensitive capability
  • set_delivery_addressno sensitive capability
  • set_delivery_slotno sensitive capability
  • set_shopping_list_item_checkedno sensitive capability
  • shopping_list_to_cartno sensitive capability
  • silpo_suggest_from_historyno sensitive capability
  • update_cart_itemno 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
v2.0.0 latest A 98/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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/silpo-mcp/badge.svg)](https://mcptrustchecker.com/registry/silpo-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/silpo-mcp"><img src="https://mcptrustchecker.com/registry/silpo-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/silpo-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 silpo-mcp --online

Use the free API → How scoring works

More in API Development