accueil / serveurs / Recherche & Web / golf.caddence/caddence
golf.caddence/caddence
serveur MCP (Model Context Protocol) · caddence 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que golf.caddence/caddence est sûr ?
Au dernier audit MCP Hub, le serveur MCP « golf.caddence/caddence » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 6 outils
- get_catalog_stats≈ 588 tokens
Live catalogue totals plus the valid values for search filters (brands, product types, conditions, flexes, hands, price range). Call this before filtered searches if unsure which brand or product_type spellings the catalogue uses.
Paramètres, retour & exemple (1)
Paramètrescontext· string · requis
Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
Exemple d'appel{"name": "get_catalog_stats", "arguments": {"context": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"hands": [], "brands": [], "flexes": [], "retailers": [], "conditions": [], "price_range": "texte", "product_types": [], "retailer_count": 1, "total_products": 1}} - get_deal_intelligence≈ 1189 tokens
Deal-quality assessment for one product: CaddenceScore (0-100 rating of the current best DEAL, not the club), price trajectory vs typical/low/high, used market stats, and per-build availability (condition/flex/loft/hand) with the cheapest retailer and a buy_url purchase link per build. Use this to answer "is this a good price right now?".
Paramètres, retour & exemple (3)
Paramètresslug· string · optionnel
Alias for product — pass eithercontext· string · requis
Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."product· string · optionnel
Product slug (preferred, from search results) or numeric product id
Exemple d'appel{"name": "get_deal_intelligence", "arguments": {"context": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "slug": "texte", "used": "texte", "brand": "texte", "score": {}, "trajectory": {}, "product_url": "texte", "availability": [], "cheapest_new": "texte"}} - get_market_deals≈ 606 tokens
Current best-value products across the UK market: largest verified price spreads between retailers (3+ retailers, false-positive filters applied). Good for "what are the best golf deals right now?". Follow up with get_product_offers for purchase links.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnelcontext· string · requis
Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."category· string · optionnel
Product type filter, e.g. "driver", "iron_set", "putter"
Exemple d'appel{"name": "get_market_deals", "arguments": {"context": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"deals": [], "total": 1}} - get_price_history≈ 776 tokens
Daily lowest/average UK price for one product over a trailing window, plus summary stats (historical low with date, high, trend direction). Optionally scoped to a variant configuration; if the variant series is too thin the backend falls back to product-level history (see scope field).
Paramètres, retour & exemple (8)
Paramètresdays· integer · optionnel
Trailing window in daysflex· string · optionnelhand· string · optionnel
e.g. "RH" or "LH"loft· string · optionnelslug· string · optionnel
Alias for product — pass eithercontext· string · requis
Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."product· string · optionnel
Product slug (preferred, from search results) or numeric product idcondition· string · optionnel · new | used
Exemple d'appel{"name": "get_price_history", "arguments": {"context": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"brand": "texte", "daily": [], "scope": "texte", "trend": "texte", "product": "texte", "days_tracked": 1, "low_in_window": "texte", "high_in_window": "texte", "current_min_price": "texte", "retailers_tracked": 1}} - get_product_offers≈ 1524 tokens
Current UK retailer offers for one product, in-stock first then cheapest, with variant details (shaft, flex, hand, loft, condition). The summary object always gives the cheapest in-stock new offer and the cheapest in-stock used offer, with counts, whatever condition is requested. Used means every second-hand condition (used, refurbished, ex-display); each offer still states its own condition. Set condition to "new" when the shopper wants a new club and "used" for second-hand; the default "all" mixes both. Each offer and each cheapest entry includes buy_url, a Caddence redirect link. Always present buy_url as the purchase link when the user wants to buy; never reconstruct or substitute retailer URLs.
Paramètres, retour & exemple (4)
Paramètresslug· string · optionnel
Alias for product — pass eithercontext· string · requis
Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."product· string · optionnel
Product slug (preferred, from search results) or numeric product idcondition· string · optionnel · new | used | all
Which offers to list: "new", "used" (any second-hand condition) or "all" (default; reserves room for both so used stock cannot hide new). Applied before the 30-offer cap.
Exemple d'appel{"name": "get_product_offers", "arguments": {"context": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "offers": [], "product": {}, "summary": {}, "returned": 1, "condition": "new", "total_offers": 1}} - search_golf_products≈ 939 tokens
Search Caddence's UK golf equipment price-comparison catalogue (clubs, balls, bags, shoes, accessories across all major UK golf retailers; prices in GBP, refreshed daily). Returns best current prices with retailer counts. When in_stock is false, price is the last seen price, not a live offer. For retailer offers and purchase links, follow up with get_product_offers using the returned slug. If unsure of valid brand or product_type values, call get_catalog_stats first.
Paramètres, retour & exemple (11)
Paramètresbrand· string · optionnel
Exact brand filter, e.g. "Titleist"limit· integer · optionnelquery· string · optionnel
Free-text search, e.g. "taylormade qi10 driver"offset· integer · optionnelcontext· string · requis
Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."on_sale· boolean · optionnel
Only products currently below RRPsort_by· string · optionnel · price_low | price_high | savings | rrp_discountcondition· string · optionnel · new | usedmax_price· number · optionnel
Maximum price in GBPmin_price· number · optionnel
Minimum price in GBPproduct_type· string · optionnel
Exact type filter, e.g. "driver", "iron_set", "putter", "balls"
Exemple d'appel{"name": "search_golf_products", "arguments": {"context": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "products": [], "returned": 1}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».