PrijsProfeet MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIJSPROFEET_API_KEY | No | PrijsProfeet API key. Sent as X-API-Key; needed for Pro endpoints and usage. | |
| PRIJSPROFEET_BASE_URL | No | API origin. Non-HTTPS is allowed only for localhost. | https://www.prijsprofeet.nl |
| PRIJSPROFEET_TIMEOUT_MS | No | Positive upstream request timeout in milliseconds. | 15000 |
| PRIJSPROFEET_USER_AGENT | No | Identifies this integration to PrijsProfeet. Uses project default if unset. | |
| PRIJSPROFEET_MCP_AUTH_TOKEN | No | Bearer token required for /mcp when running as an authenticated Streamable HTTP server. | |
| PRIJSPROFEET_MCP_BIND_ADDRESS | No | Host address and port for the HTTP server, e.g. 127.0.0.1:3000. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify that PriceProfeet services are operational. |
| list_productsC | List products with filters, sorting, and pagination. |
| get_productA | Get one product by its unique ID. |
| get_price_historyA | Get Pro price history for a product. Requires PRIJSPROFEET_API_KEY with Pro access. |
| get_forecastA | Get the backtested price forecast for a product, if enough history exists. |
| search_products_by_nameA | Search the product collection by name with an optional retailer filter. |
| get_products_by_folderB | Get products from a folder with pagination. |
| get_products_by_retailerA | Get products for one retailer with pagination. |
| get_promotional_productsB | Get promotional products, optionally filtered by retailer. |
| search_productsA | Fuzzy search and browse promotions with retailer, category, status, type, dietary, price, savings, sorting, and pagination filters. |
| get_categoriesA | Get unified product categories and product counts. |
| get_filter_statsB | Get faceted counts for matching retailers, statuses, categories, and dietary tags. |
| match_by_eanA | Find products with the same EAN across retailers. Pro API key required. Non-current matches may be upcoming or historical unless current_only is true. |
| match_productA | Find a product at other retailers. Pro API key required. Non-current matches may be upcoming or historical unless current_only is true. |
| compare_pricesA | Compare an EAN across retailers. Pro API key required; inspect promotion status and validity before presenting a current cheapest price. |
| get_ean_statsA | Get EAN coverage statistics across retailers. Pro API key required. |
| get_top_dealsA | Get top deals by savings percentage and amount, optionally scoped to repeatable retailer slugs. |
| get_brand_dealsB | Get current deal variants for a brand. |
| get_deals_summaryB | Get aggregate deal and retailer statistics. |
| get_popular_dealsA | Get the most-clicked products from the last seven days. |
| get_deals_by_typeB | Get products matching a promotion keyword such as 1+1. |
| get_new_dealsA | Get products scraped this week, newest first. |
| request_free_api_keyA | Ask PriceProfeet to email a free API-key link. Rate limited to five requests per hour per IP. |
| get_partner_usageA | Get API-key account and rate-limit usage. Requires PRIJSPROFEET_API_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.