mcp-registry/com.vendooly/vendooly · v1.0.0
As of 2026-10-18 13:07 UTC, the Vendooly MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Amazon Seller Central and Amazon Ads for AI assistants: catalog, orders, FBA, pricing, PPC.
Claude Code
claude mcp add --transport http vendooly-mcp-server https://mcp.vendooly.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"vendooly-mcp-server": {
"type": "http",
"url": "https://mcp.vendooly.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
116 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
178 parameter(s) across 84 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 →
5 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Loading this server's tool list costs an agent ~28,538 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~2,263 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 →
In the last 30 days: 0 tool(s) removed and 7 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 →
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/com.vendooly/vendooly"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.vendooly/vendooly"}) over MCP.
check_listing_restrictions ~898 tokenslist_inactive_listings ~614 tokensads_update_sb_campaign ~590 tokensads_update_sp_campaign ~568 tokensinvite_team_member ~561 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%2Fcom.vendooly%2Fvendooly?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.vendooly%2Fvendooly?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vendooly%2Fvendooly.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vendooly%2Fvendooly.svg :target: https://glimind.com/server/mcp-registry%2Fcom.vendooly%2Fvendooly?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:eca8110225678e23…, first seen 2026-10-17, included at leaf 1720 of 22,017. Version history · verify what your client received.
Compare: most reliable data servers · most reliable marketing servers · most reliable other servers · most reliable advertising servers · most reliable ads 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 13:07 UTC, the Vendooly MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Vendooly MCP server advertises 116 tools, including ads_catalog_coverage, ads_create_portfolio, ads_create_sp_ad_group, ads_create_sp_campaign, ads_create_sp_keywords.
Point your MCP client at this streamable-http endpoint: https://mcp.vendooly.com/mcp
Glimind scanned all 116 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.