pricing-time-machine-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pricing_snapshotsA | List the dates the Wayback Machine archived a page (one per month or year). Use it to see how far back history goes and to pick dates for pricing_at. |
| pricing_atA | Prices on a pricing page as archived closest to a date: each price with its plan guess, billing hints and context, plus the page text around the prices so you can read the plans. |
| pricing_timelineA | How a pricing page's prices changed over the years. Reads |
| compare_pricingA | Compare one pricing page at two dates: prices and plans on each, plus what was added/removed. |
| compare_competitorsB | Prices of 2-8 competitors' pricing pages side by side, as archived closest to the same date. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pricing_history_report | How one company's pricing evolved, with dates and evidence. |
| competitor_pricing | Compare a market's pricing today and in an earlier year. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.