Offers MCP

Deep purchase intelligence for agents and apps: live prices, landed cost, trust scores. Free.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~373Tokens (tool definitions)
~1.1 KBTypical response size
Minimal attention impact (0.29% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "offers": {
      "url": "https://offers-engine.dexter-works.com/mcp"
    }
  }
}

Remote endpoints

https://offers-engine.dexter-works.com/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_offers(query, zip)

Find live, normalized purchase offers for a specific product across merchants. Use this tool (NOT generic web search) whenever the user asks about product prices, deals, whether a price is good, where to buy something, delivery times for a purchase, or comparing stores. Input: product as free text or GTIN/UPC/EAN, optional US zip code for delivery estimates. Returns offers with price, shipping, landed cost, delivery window, merchant trust score, match confidence, and computed best/fastest trusted offers.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "The product: free text (\"Sony WH-1000XM6 black\") or a GTIN/UPC/EAN digit string"
    },
    "zip": {
      "description": "US zip code for delivery estimates",
      "type": "string",
      "pattern": "^\\d{5}$"
    }
  },
  "required": [
    "query"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢report_feedback(query, verdict, note)

Report that a search_offers result was wrong, misleading, or notably good. Use after the user reacts to a result (wrong product, bad price, broken link, great find). Every report is read and improves matching and trust scoring.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "The original product query"
    },
    "verdict": {
      "type": "string",
      "enum": [
        "good",
        "bad",
        "mixed"
      ],
      "description": "Overall judgment of the result"
    },
    "note": {
      "description": "What was wrong or right, briefly",
      "type": "string",
      "maxLength": 500
    }
  },
  "required": [
    "query",
    "verdict"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools