Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KuantoKusta

PYPI · KUANTOKUSTA-MCP

Search products and compare store prices on KuantoKusta, Portugal's price comparator.

Available components

62 Trust /100

Last scanned (5 hours ago)

Scores higher than 59% of PyPI servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ThiagoJacobLannes/kuantokusta-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 640 tokens (~320/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/kuantokusta-mcp@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ThiagoJacobLannes/kuantokusta-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ThiagoJacobLannes/kuantokusta-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0
Rekor log index 3614893579
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:945de075d795d2b97f7fb8aa9e437764377c243b1ff218bc8996a2dbbf0c0062

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~640 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_product ~137

Get full details and all store prices for a KuantoKusta product. Pass the product URL from a `search` result. Returns the product name, description, technical specs (45+ attributes), and all store offers sorted by **total price** (product + shipping) — so you always see the true cheapest option, not just the lowest sticker price. Args: url: KuantoKusta product URL from a search result, e.g. "https://www.kuantokusta.pt/p/1967884/mini-com-congelador-smeg-fa120e"

NameTypeReqDescription
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search ~503

Search for products on KuantoKusta.pt — Portugal's main price comparator. Returns up to 48 products per page plus `available_filters` showing all filter options that can be applied to narrow the results. Filters are **dynamic** and change per product type — always read `available_filters` from the response rather than guessing values. Recommended workflow: 1. Call search with just `query` (and optionally `sort`/price range). 2. Read `available_filters` in the response to see areas, brands, and product-specific filters (color, capacity, energy class, typology…). 3. Call search again with the desired filter values to get refined results. Args: query: Search keywords, e.g. "frigorífico", "iphone 15", "tv 55 polegadas". area: Top-level category — use a value from `available_filters` where field="area". Example: "Electrodomésticos", "Informática". family: Sub-category within an area — use a value from `available_filters` where field="family". Example: "Grandes Electrodomésticos". sort: "cheap" (default) | "expensive" | "popular" | "alphabetical" | "newest". price_min: Minimum price in EUR (integer). price_max: Maximum price in EUR (integer). brands: List of brand names — use values from `available_filters` where field="brand". Example: ["Samsung", "LG"]. features: Dict of product-type-specific filter values — keys and valid values come from `available_filters` where field is NOT area/family/brand. Example: {"tipologia_s": "combinados", "cor_s": "inox", "classe_energetica_s": "classe a"}. For a laptop search the keys would be different (ram_s, os_s, etc.) — always derive them from the previous call's available_filters. page: Results page number (default 1; ~48 products per page).

NameTypeReqDescription
area–––
brands–––
family–––
features–––
pageinteger––
price_max–––
price_min–––
querystringyes–
sortstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the KuantoKusta MCP server?

KuantoKusta runs locally as a PyPI package, launched with uvx kuantokusta-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · kuantokusta-mcp

# add to Claude Code
claude mcp add thiagojacoblannes-kuantokusta-mcp -- uvx kuantokusta-mcp
Common questions

What is the KuantoKusta MCP server?

KuantoKusta is an MCP server listed in the public MCP registry as io.github.ThiagoJacobLannes/kuantokusta-mcp. Search products and compare store prices on KuantoKusta, Portugal's price comparator. This page covers its PyPI package (kuantokusta-mcp).

Is the KuantoKusta MCP server safe to use?

KuantoKusta scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the KuantoKusta MCP server expose?

KuantoKusta exposes 2 tools: search, get_product. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.

Is the KuantoKusta MCP server still maintained?

KuantoKusta is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the KuantoKusta MCP server under?

KuantoKusta declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the KuantoKusta MCP server?

VerifyMCP ran 14 checks on KuantoKusta, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about KuantoKusta: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.