# ReturnCheck (npm · returncheck-mcp)

Can this product actually be returned? The merchant's exact clause, its URL and the date.

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `returncheck.m-angelmartinez-fer.workers.dev`: 69/100, [markdown](https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck.md), [page](https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck)
- npm · `returncheck-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck-mcp.md), [page](https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck-mcp)

## Channel facts

- Registry: `npm`
- Package: `returncheck-mcp`
- Version: `0.1.1`
- 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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **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 22 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 396 tokens (~396/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

ReturnCheck runs locally as an npm package, launched with npx -y returncheck-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 mangelmartinezfer-hue-returncheck -- npx -y returncheck-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mangelmartinezfer-hue-returncheck": {
      "command": "npx",
      "args": [
        "-y",
        "returncheck-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mangelmartinezfer-hue-returncheck": {
      "command": "npx",
      "args": [
        "-y",
        "returncheck-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mangelmartinezfer-hue-returncheck -- npx -y returncheck-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mangelmartinezfer-hue-returncheck": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "returncheck-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mangelmartinezfer-hue-returncheck --command npx --arg -y --arg returncheck-mcp
```

### Hermes

```yaml
mcp_servers:
  mangelmartinezfer-hue-returncheck:
    command: "npx"
    args: ["-y", "returncheck-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mangelmartinezfer-hue-returncheck": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "returncheck-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mangelmartinezfer-hue-returncheck -t stdio -c npx -a -y returncheck-mcp
```

### Other

```json
{
  "mcpServers": {
    "mangelmartinezfer-hue-returncheck": {
      "command": "npx",
      "args": [
        "-y",
        "returncheck-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-09-20 (score 77, +1)

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

### 2026-09-18 (score 76, +1)

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

### 2026-09-16 (score 75, +1)

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

### 2026-09-14 (score 74, +1)

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

### 2026-09-11 (score 73, +1)

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

### 2026-09-09 (score 72, +1)

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

### 2026-09-07 (score 71, +1)

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

### 2026-09-05 (score 70, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (1)

### `check_return` (~316 tokens)

Answer one question: can this specific product actually be returned? Give a product_url and buyer_country and you get a verified verdict — YES / YES_WITH_CONDITIONS / NO / UNKNOWN — with the exact policy clause quoted verbatim, the source URL, the return window and a confidence score. Coverage, measured not claimed: on 50 real US retailers (frozen list, 2026-08-28) the policy was reached for 17. The rest are stores that serve no policy text to anything but a real browser. Pass page_text yourself and those work too. Never invents: returns UNKNOWN instead of guessing, and UNKNOWN is free.

Input parameters:

- `buyer_country` (string, required): ISO 3166-1 alpha-2, e.g. 'US'.
- `delivery_date` (string): YYYY-MM-DD (optional; preferred for the deadline).
- `item_condition` (string)
- `membership` (string): Loyalty tier, if the buyer has one (e.g. 'Plus').
- `merchant` (string)
- `page_html` (string): Optional: raw HTML, if you already have it.
- `page_text` (string): Optional: the page text, if you already have it. If omitted, this package fetches it locally.
- `product_url` (string, required): The product page URL (http/https).
- `purchase_channel` (string)
- `purchase_date` (string): YYYY-MM-DD (optional).
- `reason` (string)
- `seller_name` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck-mcp#diagnostics

## Score history

- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 66
- 2026-09-01: 66
- 2026-08-31: 66
- 2026-08-30: 66
- 2026-08-29: 66
- 2026-08-28: 66

## Common questions

### What is the ReturnCheck MCP server?

ReturnCheck is an MCP server listed in the public MCP registry as io.github.mangelmartinezfer-hue/returncheck. Can this product actually be returned? The merchant's exact clause, its URL and the date. This page covers its npm package (returncheck-mcp).

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

ReturnCheck scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 ReturnCheck MCP server expose?

ReturnCheck exposes 1 tool: check_return. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.

### Is the ReturnCheck MCP server still maintained?

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

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

## Links

- npm package: https://www.npmjs.com/package/returncheck-mcp
- Socket report: https://socket.dev/npm/package/returncheck-mcp
- Repository: https://github.com/mangelmartinezfer-hue/returncheck
- Website: https://returncheck.m-angelmartinez-fer.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mangelmartinezfer-hue-returncheck/returncheck-mcp