ReturnCheck

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

我该使用它吗

质量与安全性

A
描述质量
100%
模式完整度
93%
命名质量
100%
投毒风险
100%
权限匹配度
100%
协议合规性
100%

基于对工具定义和协议合规性的自动分析。

上下文开销

~566token 数(工具定义)
~5.0 KB典型响应大小
对注意力的影响极小(占 128k 上下文窗口的 0.44%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

{
  "mcpServers": {
    "returncheck": {
      "command": "npx",
      "args": [
        "returncheck-mcp"
      ]
    }
  }
}

可运行的软件包

npmreturncheck-mcp0.1.1stdio

远程端点

https://returncheck.m-angelmartinez-fer.workers.dev/mcpstreamable-http

它能做什么

工具清单

工具(1)

🟢 只读🟡 写入🔴 删除⚪ 未知
🟡check_return(product_url, buyer_country, item_condition, reason, purchase_date, ...)

Answer one question: can this specific product actually be returned? BEST RESULTS: send the product page you already have as page_text (or page_html) along with product_url — your browser renders JavaScript and is not blocked by retailers, so this works on any store and is faster. Without it we fetch the page ourselves and reach the policy for about 1 in 3 US retailers (17 of 50 measured 2026-08-28; mostly Shopify and direct-to-consumer brands — large retailers and marketplaces block server-side reads). You get a verified verdict — YES / YES_WITH_CONDITIONS / NO / UNKNOWN — with the exact policy clause quoted verbatim, source URL, return window/deadline, fees and a confidence score. Never invents: returns UNKNOWN instead of guessing, and UNKNOWN is free.

输入模式

{
  "type": "object",
  "properties": {
    "product_url": {
      "type": "string",
      "description": "The product page URL (http/https)."
    },
    "buyer_country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2, e.g. 'US'."
    },
    "item_condition": {
      "type": "string",
      "enum": [
        "unopened",
        "opened",
        "used",
        "defective"
      ]
    },
    "reason": {
      "type": "string",
      "enum": [
        "changed_mind",
        "defective",
        "wrong_size_or_model",
        "arrived_late",
        "other"
      ]
    },
    "purchase_date": {
      "type": "string",
      "description": "YYYY-MM-DD (optional)."
    },
    "delivery_date": {
      "type": "string",
      "description": "YYYY-MM-DD (optional; preferred for the deadline)."
    },
    "merchant": {
      "type": "string"
    },
    "seller_name": {
      "type": "string"
    },
    "page_text": {
      "type": "string",
      "description": "RECOMMENDED. Plain text of the product or returns page you already have open. We verify against this instead of fetching: works on any store, no blocking, no JavaScript problem, and faster. Still never invents: no verifiable clause -> UNKNOWN (free)."
    },
    "page_html": {
      "type": "string",
      "description": "RECOMMENDED (alternative to page_text). Raw HTML of the same page. Slightly better than page_text: we can also read structured data (JSON-LD) from it."
    },
    "payment_signature": {
      "type": "string",
      "description": "OPTIONAL. x402 payment authorization, base64 — the same envelope the PAYMENT-SIGNATURE header carries over HTTP. Use it to pay per call with no account and no signup. How: call once without it; if the free trial is exhausted you get the payment terms in structuredContent (x402Version, accepts[]); sign that authorization and call again with payment_signature set. Terms are also published at /.well-known/x402. UNKNOWN verdicts are never settled: the authorization simply expires unused."
    }
  },
  "required": [
    "product_url",
    "buyer_country"
  ]
}

社区

评价此服务器

证据

最近观测

已验证未记录版本1 个工具
已验证未记录版本1 个工具