Skip to main content
Glama
theluckystrike

price-tracker

by theluckystrike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to price-tracker

No user-submitted related servers found.

    Related Servers

    • ru-marketplace-mcp

      Vladimir-Human
      A
      license
      A
      quality
      A
      maintenance
      MCP server that reads product data from Russian and Chinese marketplaces (Wildberries, Ozon, Yandex Market, Avito, etc.) — prices, availability, ratings, reviews, and seller details — with price comparison across sources. Requires no API keys; some sources use your Chrome session for anti-bot access.
      2
      40
      166
      MIT

    • Amazon Price Tracker MCP

      aravindtri
      A
      license
      A
      quality
      D
      maintenance
      MCP server for tracking Amazon product prices via camelcamelcamel.com, using headless Chromium to bypass Cloudflare protection.
      3
      1
      ISC

    • telegram-api-mcp

      timoncool
      A
      license
      C
      quality
      C
      maintenance
      Ultimate MCP server for Telegram Bot API — 169 methods, full v9.6 coverage, meta-mode, rate limiting, and circuit breaker, enabling AI to control Telegram bots with natural language.
      100
      34
      MIT

    • M.Video MCP

      richtargetman
      F
      license
      A
      quality
      B
      maintenance
      Local MCP server for M.Video/Eldorado OmniNet seller API, enabling price/stock updates, product mappings, FBS orders, and shipment management.
      12
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: watch_* handles persistent tracking, price_check is a stateless one-off lookup, and license_* covers licensing. The only real overlap is watch_add vs price_check, which both accept a product URL and fetch a price, but descriptions explicitly separate them ('creates no watch' vs 'starts tracking').

    Naming Consistency4/5

    A dominant domain-prefix pattern runs throughout (watch_, price_, alerts_, license_), which makes grouping intuitive. Minor deviations exist: alerts_pending and license_status are noun/adjective forms rather than the verb-style used by the rest.

    Tool Count5/5

    Ten tools is well within the ideal range and each earns its place: tracking CRUD, refresh, history, alerts, one-off check, and licensing are all genuinely distinct operations. No redundancy or filler.

    Completeness4/5

    The lifecycle is well covered: add, list, refresh, history, alerts, remove, manual entry, one-off check, plus license handling. Minor gaps remain, such as no tool to update an existing watch's target_price or bulk-remove watches, but these are workable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources