mcp-registry/io.github.mangelmartinezfer-hue/returncheck · v1.0.0
As of 2026-10-21 15:24 UTC, the Mangelmartinezfer Hue Returncheck MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Can this product actually be returned? The merchant's exact clause, its URL and the date.
Claude Code
claude mcp add --transport http mangelmartinezfer-hue-returncheck-mcp-se https://returncheck.m-angelmartinez-fer.workers.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mangelmartinezfer-hue-returncheck-mcp-se": {
"type": "http",
"url": "https://returncheck.m-angelmartinez-fer.workers.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mangelmartinezfer-hue%2Freturncheck/fixes
{
"name": "check_return",
"description": "ReturnCheck verifies which return policy actually applies to this purchase. 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 serv",
"inputSchema": {
"type": "object",
"required": [
"product_url",
"buyer_country"
],
"properties": {
"reason": {
"enum": [
"changed_mind",
"defective",
"wrong_size_or_model",
"arrived_late",
"other"
],
"type": "string"
},
"merchant": {
"type": "string"
},
"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."
},
"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)."
},
"product_url": {
"type": "string",
"description": "The product page URL (http/https)."
},
"seller_name": {
"type": "string"
},
"buyer_country": {
"type": "string",
"description": "ISO 3166-1 alpha-2, e.g. 'US'."
},
"delivery_date": {
"type": "string",
"description": "YYYY-MM-DD (optional; preferred for the deadline)."
},
"purchase_date": {
"type": "string",
"description": "YYYY-MM-DD (optional)."
},
"item_condition": {
"enum": [
"unopened",
"opened",
"used",
"defective"
],
"type": "string"
},
"page_source_url": {
"type": "string",
"description": "URL of the supplied page_text/page_html when different from product_url. Caller-declared provenance; not independently fetched."
},
"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."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mangelmartinezfer-hue/returncheck"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mangelmartinezfer-hue/returncheck"}) over MCP.
check_return ~677 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.mangelmartinezfer-hue%2Freturncheck?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mangelmartinezfer-hue%2Freturncheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mangelmartinezfer-hue%2Freturncheck.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mangelmartinezfer-hue%2Freturncheck.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mangelmartinezfer-hue%2Freturncheck?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:daf5a2466f48b04c…, first seen 2026-10-17, included at leaf 5322 of 40,246. Version history · verify what your client received.
Compare: most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 15:24 UTC, the Mangelmartinezfer Hue Returncheck MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mangelmartinezfer Hue Returncheck MCP server advertises 1 tool, including check_return.
Point your MCP client at this streamable-http endpoint: https://returncheck.m-angelmartinez-fer.workers.dev/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.