PrijsProfeet MCP
Related Servers
Alternatives to PrijsProfeet MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server exposing quote and live cryptocurrency price tools, with both local (stdio) and cloud-deployed (HTTP) transports.2MIT
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
- AlicenseNot gradedqualityBmaintenanceMCP server that provides tools to retrieve weather information from a weather API, supporting both local stdio and remote Streamable HTTP transports.221 npm1MIT
- FlicenseNot gradedqualityCmaintenanceA production-oriented MCP server exposing tools for weather, currency conversion, text statistics, and server introspection, with auto-discovery, rate limiting, and API key auth.-
- FlicenseAqualityCmaintenanceA minimal MCP server for DataProbe data question answering and read-only SQL queries, supporting stdio and streamable HTTP modes.5-
- FlicenseNot gradedqualityCmaintenanceA modular MCP server built with FastAPI, exposing tools via HTTP endpoints with SSE streaming responses.-
TDQS
Scored across 24 tools
Several tools overlap in purpose, notably list_products, search_products, and search_products_by_name, as well as multiple get_products_by_* variants. Descriptions and filters help clarify, but an agent could easily mis-select between similar list/search endpoints.
Tool names follow a uniform verb_noun pattern with snake_case (e.g., get_product, search_products, compare_prices, request_free_api_key). Prefixes like get/list/search/match/compare are used predictably, making the set highly consistent.
At 24 tools, the server sits at the upper boundary of 'heavy' but remains within the acceptable range. The many deal-related tools (top_deals, brand_deals, deals_summary, etc.) could be consolidated, but the count is justifiable for a comprehensive price-comparison API.
The tool set covers the core read-only domain well: product search, details, price history, forecasting, cross-retailer matching, price comparison, deals, categories, and API key management. Minor gaps exist (e.g., no direct retailer metadata endpoint), but no critical dead ends are evident.