ReturnCheck
Can this product actually be returned? The merchant's exact clause, its URL and the date.
사용해야 할까요
품질 및 안전성
도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.
컨텍스트 비용
이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.
설치
원클릭 설치
`claude_desktop_config.json` 파일에 다음을 추가하세요:
{
"mcpServers": {
"returncheck": {
"command": "npx",
"args": [
"returncheck-mcp"
]
}
}
}실행 가능한 패키지
0.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"
]
}커뮤니티
증거