aukro-mcp
Related Servers
Alternatives to aukro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceRemote MCP server (Streamable HTTP) that reads and parses the public catalog website atcmarket.cz (AT Computers) to enable product search, category-filtered search, supported filter listing, product detail lookup, and cross-product comparison — without login or state.-
- AlicenseAqualityCmaintenanceMCP server for interacting with Bazos.cz, Bazos.sk, Bazos.at, and Bazos.pl. Supports searching ads, retrieving ad details, and fetching user ratings.386 npm4AGPL 3.0
- AlicenseBqualityCmaintenanceA production-ready MCP server offering text analysis tools, an in-memory key-value store, and system info resources with support for both stdio and HTTP transports.4MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that provides Hugging Face Hub API and Search endpoints through multiple transport protocols (STDIO, SSE, StreamableHTTP, and StreamableHTTPJson), enabling integration with AI model capabilities.314MIT
- FlicenseNot gradedqualityDmaintenanceA simple MCP server for interacting with Trade Me APIs, providing tools for connectivity testing and SDK integration.-
TDQS
Scored across 25 tools
Most tools have clearly distinct purposes (search vs autocomplete, offer detail vs status batch vs bids, watchlist vs favourites, buyer vs seller views). A few pairs like get_offer_detail/get_offers_status_batch and my_bids_and_purchases/my_sales could be momentarily confused, but descriptions clarify the boundaries.
All tools use the aukro_ prefix and snake_case, with mostly verb_noun patterns (search_offers, get_categories, place_bid, manage_offer). A handful of noun-only multi-action tools (watchlist, cart, messages, my_account, offer_templates) deviate slightly but follow a coherent convention.
25 tools is heavy and sits at the upper boundary of the rubric's 'borderline' range. While each tool covers a distinct function across a full marketplace domain, the surface feels large and could likely be consolidated.
The set covers a broad marketplace lifecycle: browsing/search, offer detail, bidding, cart, seller offer management, messaging, and user info. Notable gaps remain (no checkout/order finalization, no feedback submission, no way to save a new search despite listing/removing saved searches), but core workflows are usable.