# Unfret (pypi · unfret-mcp)

Checks a store, marketplace seller or listing for scam signals before an agent buys, paid per check

- Trust score: 57/100 (low)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `unfret.net`: 33/100, [markdown](https://verifymcp.io/servers/net-unfret-mcp/unfret.md), [page](https://verifymcp.io/servers/net-unfret-mcp/unfret)
- pypi · `unfret-mcp`: 57/100 (this document), [markdown](https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp.md), [page](https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp)

## Channel facts

- Registry: `pypi`
- Package: `unfret-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs uv_build at install time, a recognised build step with no custom scripting around it.
  - 2 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 614 tokens (~204/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Unfret MCP server?

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

### Claude

```bash
claude mcp add net-unfret-mcp -- uvx unfret-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "net-unfret-mcp": {
      "command": "uvx",
      "args": [
        "unfret-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-unfret-mcp": {
      "command": "uvx",
      "args": [
        "unfret-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add net-unfret-mcp -- uvx unfret-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-unfret-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "unfret-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-unfret-mcp --command uvx --arg unfret-mcp
```

### Hermes

```yaml
mcp_servers:
  net-unfret-mcp:
    command: "uvx"
    args: ["unfret-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "net-unfret-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "unfret-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-unfret-mcp -t stdio -c uvx -a unfret-mcp
```

### Other

```json
{
  "mcpServers": {
    "net-unfret-mcp": {
      "command": "uvx",
      "args": [
        "unfret-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 57, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 56, 0)

- [functional regression] Schema quality: 177 → 204
- [functional] Package version: 0.1.1 → 0.2.0

### 2026-11-17 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 55, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 69, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-11-12 (score 53)

First indexed and scored.

## MCP tools (3)

### `check_store` (~341 tokens)

Check a store or listing

Check a store or product page for scam, dropshipping and dark-pattern risk. Paid per call in USDC or wSOL.

Pass page_content (the page's HTML) for marketplaces such as Amazon, which block server-side fetches.

:param url: The store or product page URL.
:param tier: quick (cheap checks, $0.01) or deep (everything incl. reverse image search, $0.20).
:param policy: How cautious the returned action is: strict, balanced or lenient.
:param page_content: The page's HTML, if available.
:return: ``status`` (ok, not_paid, pending, unknown, unavailable), ``ok``, the ``verdict`` (action, risk_score,
    confidence, flags, and ``band``: what a shopper is shown, ``reliable`` "Looks fine", ``concerns`` "Worth a
    look", ``careful`` "Think twice" or ``junk_or_scam`` "Serious concerns") or ``error``, the payment, and
    ``next_step`` when there's something to do.

Input parameters:

- `page_content`: The page's HTML, if you have it. Needed for marketplaces such as Amazon, which block fetches.
- `policy` (string): How cautious the returned action is; strict warns and blocks soonest.
- `tier` (string): quick: rule checks on the page itself, $0.01. deep: everything, including an LLM reading of the page, reviews, domain age and reverse image search, $0.20.
- `url` (string, required): The store or product page URL (https).

### `get_pricing` (~88 tokens)

Unfret prices

Unfret's current prices (free, no payment): the check tiers in dollars, and the live USDC and SOL amounts.

:return: ``status``, ``ok`` and the price list (``x402``: ``quick_usd_micros``, ``deep_usd_micros``; ``usdc``;
    ``sol``), or ``error``.

### `explain_flag` (~62 tokens)

Explain a flag

Explain what a flag in an Unfret verdict means, in one paragraph for the end user.

:param flag_type: The flag's ``type``.
:return: The explanation.

Input parameters:

- `flag_type` (string, required): A flag's `type` from a verdict.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp#diagnostics

## Score history

- 2026-11-21: 57
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 56
- 2026-11-17: 56
- 2026-11-16: 55
- 2026-11-15: 55
- 2026-11-14: 69
- 2026-11-13: 53
- 2026-11-12: 53

## Common questions

### What is the Unfret MCP server?

Unfret is an MCP server listed in the public MCP registry as net.unfret/mcp. Checks a store, marketplace seller or listing for scam signals before an agent buys, paid per check. This page covers its PyPI package (unfret-mcp).

### Is the Unfret MCP server safe to use?

Unfret scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Unfret MCP server expose?

Unfret exposes 3 tools: check_store, get_pricing, explain_flag. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.

### Is the Unfret MCP server still maintained?

Unfret is still listed as active in the MCP registry. We last reached this channel on 21 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 Unfret MCP server under?

Unfret 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 Unfret MCP server?

VerifyMCP ran 15 checks on Unfret, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Unfret: Malware scan. 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.

## Links

- PyPI project: https://pypi.org/project/unfret-mcp/
- Socket report: https://socket.dev/pypi/package/unfret-mcp
- Repository: https://github.com/kroshtan/unfret_backend
- Website: https://unfret.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp.json
- HTML version of this page: https://verifymcp.io/servers/net-unfret-mcp/unfret-mcp
