mcp-registry/io.github.ryanyang828/listinggood · v1.9.4
Also listed as github/ryanyang828/listinggood-skills, glama/ryanyang828/listinggood-mcp
As of 2026-10-22 21:50 UTC, the Ryanyang828 Listinggood MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 74 outages in 90 days, with a median recovery of 7 minutes.
Get recommended by Amazon's AI. Hosted MCP server for Amazon listing compliance & generation.
Claude Code
claude mcp add --transport http ryanyang828-listinggood-mcp-server https://listinggood.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ryanyang828-listinggood-mcp-server": {
"type": "http",
"url": "https://listinggood.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
29 parameter(s) across 8 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 →
8 of 8 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 →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Handshake + tools/list takes ~2,704 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ryanyang828%2Flistinggood/fixes
{
"name": "agent_ready_check",
"description": "Score whether a product listing is Agent-Ready for AI shopping agents (ACP/UCP era).\n\n Platform-agnostic: works for Amazon, Shopify, Walmart, TikTok Shop or any storefront that\n AI shopping assistants may read. Use it when a user asks whether their product will be\n found, recommended, or auto-purchased by an AI agent.\n\n Fully local, deterministic rule engine — no API key, no credits, no network call. Returns\n four dimensions: structured attributes, entity clarity, trust & complian",
"inputSchema": {
"type": "object",
"title": "agent_ready_checkArguments",
"required": [
"text"
],
"properties": {
"lang": {
"type": "string",
"title": "Lang",
"default": "en"
},
"text": {
"type": "string",
"title": "Text"
},
"platform": {
"type": "string",
"title": "Platform",
"default": "auto"
}
}
},
"annotations": {
"read_only_hint": true,
"idempotent_hint": true,
"open_world_hint": false,
"destructive_hint": false,
"readOnlyHint": true
}
}{
"name": "ai_readiness_check",
"description": "Score how likely Amazon's AI (Rufus, COSMO) is to recommend a listing.\n\n Free, deterministic, rule-based check on pasted listing copy (title, bullets, description).\n Returns a compliance health score, an AI-readability score, and a combined AI Recommendation\n Readiness Score (compliance * 0.55 + readability * 0.45) with actionable suggestions.\n\n Use this as a fast baseline BEFORE generating or editing a listing. Do NOT use it for a full\n compliance report - use compliance_scan for",
"inputSchema": {
"type": "object",
"title": "ai_readiness_checkArguments",
"required": [
"text"
],
"properties": {
"lang": {
"type": "string",
"title": "Lang",
"default": "en"
},
"text": {
"type": "string",
"title": "Text"
},
"email": {
"type": "string",
"title": "Email",
"default": ""
},
"marketplace": {
"type": "string",
"title": "Marketplace",
"default": "US"
}
}
},
"annotations": {
"read_only_hint": true,
"idempotent_hint": false,
"open_world_hint": true,
"destructive_hint": false,
"readOnlyHint": true
}
}{
"name": "analyze_review",
"description": "Analyze a negative Amazon review for root cause and a suggested response (async; 2 credits).\n\n Extracts the underlying issue from a critical review and drafts a brand-appropriate response\n angle. Use this after a negative review appears, to decide how to reply. Do NOT use it to\n generate a listing or an appeal - use generate_listing or generate_poa for those. Read-only;\n deducts 2 credits; runs asynchronously, poll for the result.\n\n Args:\n text: the negative review text (re",
"inputSchema": {
"type": "object",
"title": "analyze_reviewArguments",
"required": [
"text"
],
"properties": {
"lang": {
"type": "string",
"title": "Lang",
"default": "en"
},
"text": {
"type": "string",
"title": "Text"
},
"marketplace": {
"type": "string",
"title": "Marketplace",
"default": "US"
}
}
},
"annotations": {
"read_only_hint": true,
"idempotent_hint": false,
"open_world_hint": true,
"destructive_hint": false,
"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.ryanyang828/listinggood"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.ryanyang828/listinggood"}) over MCP.
compliance_scan ~264 tokensgenerate_listing ~262 tokensgenerate_poa ~246 tokensai_readiness_check ~244 tokensagent_ready_check ~227 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.ryanyang828%2Flistinggood?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ryanyang828%2Flistinggood?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ryanyang828%2Flistinggood.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ryanyang828%2Flistinggood.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.ryanyang828%2Flistinggood?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:782ec7850d6aec06…, first seen 2026-10-17, included at leaf 11125 of 48,329. Version history · verify what your client received.
Compare: most reliable other servers · most reliable communication servers · most reliable knowledge servers · most reliable productivity 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-22 21:50 UTC, the Ryanyang828 Listinggood MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 74 outages in 90 days, with a median recovery of 7 minutes.
Ryanyang828 Listinggood MCP server advertises 8 tools, including agent_ready_check, ai_readiness_check, analyze_review, compliance_check, compliance_scan.
Point your MCP client at this streamable-http endpoint: https://listinggood.com/mcp
Glimind scanned all 8 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.