mcp-registry/io.github.48x-ai/marketbasketanalysis-mcp · v0.7.0
As of 2026-10-18 12:45 UTC, the 48x Ai Marketbasketanalysis MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 8 minutes.
Co-purchase intelligence and merchant ops tools for AI shopping, ecommerce, and B2B agents
Claude Code
claude mcp add --transport http 48x-ai-marketbasketanalysis-mcp-server https://mcp.marketbasketanalysis.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"48x-ai-marketbasketanalysis-mcp-server": {
"type": "http",
"url": "https://mcp.marketbasketanalysis.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
19 of 19 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 →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,266 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. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.48x-ai%2Fmarketbasketanalysis-mcp/fixes
{
"name": "analyze_basket",
"description": "Run market-basket analysis on a proposed basket / bundle to score its cohesion. Given 2+ products, returns a cohesion score 0..1 representing how strongly they bind together (their affinity) in the merchant's order data. Use this to vet a proposed bundle BEFORE recommending it, so agents can avoid suggesting bundles that look plausible but have no statistical signal. Also useful for 'is this a good bundle?', 'analyze this basket', or 'do these products go together?' questions.",
"inputSchema": {
"type": "object",
"required": [
"product_ids"
],
"properties": {
"product_ids": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 6,
"minItems": 2,
"description": "The products in the proposed basket (2-6)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "execute_weekly_plan_action",
"description": "Execute a specific action from the merchant's weekly plan (publish bundle, run mining job, archive rule, etc.). Idempotent by action_id, safe to retry. Use this AFTER the merchant has confirmed which action from get_weekly_plan they want to run; do not call preemptively.",
"inputSchema": {
"type": "object",
"required": [
"action_id",
"confirm"
],
"properties": {
"confirm": {
"type": "boolean",
"default": false,
"description": "Must be true to actually execute. Guard against accidental dispatch."
},
"action_id": {
"type": "string",
"description": "The id of the action to execute, from get_weekly_plan."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "explain_drift",
"description": "Explain ONE drift alert: return its prior and current confidence (plus support, lift, and order sample count when the rule is still live) and a short plain-language narrative of how the pair moved versus the prior mining run. Use this when a merchant asks 'why did this pair drift?', 'explain this alert', or 'what changed for these two products?' after seeing it in get_drift_alerts. Different from get_drift_alerts: that lists the feed, this drills into a single alert_id with the change spelled ou",
"inputSchema": {
"type": "object",
"required": [
"alert_id"
],
"properties": {
"alert_id": {
"type": "string",
"description": "The id of the drift alert to explain, from get_drift_alerts."
}
}
},
"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.48x-ai/marketbasketanalysis-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.48x-ai/marketbasketanalysis-mcp"}) over MCP.
propose_subscription_bundle ~452 tokensmine_hui_itemsets ~334 tokensscore_return_risk ~329 tokenspredict_reorder ~288 tokensfind_substitutes ~264 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.48x-ai%2Fmarketbasketanalysis-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.48x-ai%2Fmarketbasketanalysis-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.48x-ai%2Fmarketbasketanalysis-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.48x-ai%2Fmarketbasketanalysis-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.48x-ai%2Fmarketbasketanalysis-mcp?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:c54a85054f2009b9…, first seen 2026-10-17, included at leaf 13778 of 21,932. Version history · verify what your client received.
Compare: most reliable data servers · most reliable productivity servers · most reliable ml 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-18 12:45 UTC, the 48x Ai Marketbasketanalysis MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 8 minutes.
48x Ai Marketbasketanalysis MCP server advertises 19 tools, including analyze_basket, execute_weekly_plan_action, explain_drift, explain_opportunity, find_substitutes.
Point your MCP client at this streamable-http endpoint: https://mcp.marketbasketanalysis.com/mcp
Glimind scanned all 19 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.