Skip to main content
Glama
alialtunar

pricing-time-machine-mcp

by alialtunar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pricing-time-machine-mcp

No user-submitted related servers found.

    Related Servers

    • price-watch

      comparedge
      A
      license
      Not graded
      quality
      C
      maintenance
      A dated log of SaaS price changes across 494 tools: old price, new price and verification date for every move, plus category-level pulse and the biggest recorded increases.
      36 npm
      2
      MIT

    • CostBench MCP Server

      aadilr
      A
      license
      A
      quality
      B
      maintenance
      Enables access to verified software-pricing intelligence for over 3,290 products, including true costs, hidden fees, negotiation data, price history, and TCO calculations, all sourced and dated.
      8
      6 npm
      MIT

    • pricetrack-mcp

      PriceTrack-dev
      A
      license
      A
      quality
      B
      maintenance
      MCP server for PriceTrack that enables AI assistants to search live SaaS pricing, view verified price changes, and compare products side-by-side across 33,000+ vendors.
      4
      34 npm
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct query shape: listing archive dates, prices at one date, history over a range, two-date comparison, and multi-competitor comparison. There is mild overlap since pricing_at, pricing_timeline, and compare_pricing all return pricing data, but the descriptions make the boundaries (single vs. range vs. two-date vs. multi-page) clear enough to pick correctly.

    Naming Consistency4/5

    Names split into a coherent pricing_* family (snapshots, at, timeline) for single-page temporal queries and a compare_* family for comparisons, which is readable and predictable. It is not a strict single verb_noun convention (pricing_at is noun_preposition), so it's slightly short of perfect.

    Tool Count5/5

    Five tools is well-scoped for a niche Wayback pricing-history server, with each tool earning its place by covering a distinct query pattern. No redundant or filler tools.

    Completeness5/5

    The surface covers the full read-only lifecycle: discovering available dates, reading prices at a point, tracking a single page's history, comparing two dates of the same page, and comparing competitors at a common date. There are no obvious dead ends for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources