returncheck-mcp

MCPcommunitylive
v0.1.1io.github.mangelmartinezfer-hueMITUpdated 18d agonpmGitHub

MCP server for ReturnCheck — can this specific product actually be returned? Verified verdicts with the merchant's exact policy clause, the source URL and the date. Handles the cases a per-domain rating cannot: seller, membership, item condition, channel.

Endpoint healthlive
checked 2 days ago · 232ms
100% of the last 3 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
34Downloads/wk
18d agoLast update
Reads these credentials
  • RETURNCHECK_API_KEYAPI keyoptional

    Optional API key. Without it you get the keyless free trial.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.mangelmartinezfer-hue
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 0 resolved · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv0.1.1 · 14d agoHow well does this scan work?
EvalsNone
IndexedAug 28, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged
Statically extracted from the published packagev0.1.1 · 14d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

check_returnAnswer one question: can this specific product actually be returned?

Answer one question: can this specific product actually be returned?

No input schema was published for this tool.

1 of 1 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for ReturnCheck — can this specific product actually be returned? Verified verdicts with the merchant's exact policy clause, the source URL and the date. Handles the cases a per-domain rating cannot: seller, membership, item condition, channel.

Keywords
mcpmodel-context-protocolreturnsreturn-policyecommerceshoppingai-agentsagentic-commercex402returncheck
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.

Topics

Related in payments & commerce