# Pricing Time Machine (pypi · pricing-time-machine-mcp)

How any SaaS pricing page changed over the years, from the Wayback Machine. No API keys.

- Trust score: 71/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `pricing-time-machine-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/alialtunar-pricing-time-machine-mcp/pricing-time-machine-mcp.md), [page](https://verifymcp.io/servers/alialtunar-pricing-time-machine-mcp/pricing-time-machine-mcp)

## Channel facts

- Registry: `pypi`
- Package: `pricing-time-machine-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 33 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 771 tokens (~154/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Pricing Time Machine MCP server?

Pricing Time Machine runs locally as a PyPI package, launched with uvx pricing-time-machine-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add alialtunar-pricing-time-machine-mcp -- uvx pricing-time-machine-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "alialtunar-pricing-time-machine-mcp": {
      "command": "uvx",
      "args": [
        "pricing-time-machine-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alialtunar-pricing-time-machine-mcp": {
      "command": "uvx",
      "args": [
        "pricing-time-machine-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alialtunar-pricing-time-machine-mcp -- uvx pricing-time-machine-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alialtunar-pricing-time-machine-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "pricing-time-machine-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alialtunar-pricing-time-machine-mcp --command uvx --arg pricing-time-machine-mcp
```

### Hermes

```yaml
mcp_servers:
  alialtunar-pricing-time-machine-mcp:
    command: "uvx"
    args: ["pricing-time-machine-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "alialtunar-pricing-time-machine-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "pricing-time-machine-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alialtunar-pricing-time-machine-mcp -t stdio -c uvx -a pricing-time-machine-mcp
```

### Other

```json
{
  "mcpServers": {
    "alialtunar-pricing-time-machine-mcp": {
      "command": "uvx",
      "args": [
        "pricing-time-machine-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 71, 0)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 71, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 85, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 70, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-27 (score 84, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 69, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-24 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `pricing_snapshots` (~140 tokens)

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.

Input parameters:

- `from_year`: Optional year bound, e.g. 2019.
- `per` (string): One capture per 'month' (default) or 'year'.
- `response_format` (string): 'markdown' (default) or 'json'.
- `to_year`: Optional year bound, e.g. 2019.
- `url` (string, required): Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'.

Output parameters:

- `result` (string)

### `pricing_at` (~141 tokens)

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.

Input parameters:

- `date` (string): 'YYYY', 'YYYY-MM', 'YYYY-MM-DD' or 'latest'. The closest archived copy is used.
- `max_text_chars` (integer): Page text around the prices to include (0 = none).
- `response_format` (string): 'markdown' (default) or 'json'.
- `url` (string, required): Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'.

Output parameters:

- `result` (string)

### `pricing_timeline` (~144 tokens)

How a pricing page's prices changed over the years. Reads `points` archived copies spread
across the range, groups identical price sets into periods and lists what was added/removed.

Input parameters:

- `from_year`: Optional year bound, e.g. 2019.
- `points` (integer): How many copies to read across the range (more = slower).
- `response_format` (string): 'markdown' (default) or 'json'.
- `to_year`: Optional year bound, e.g. 2019.
- `url` (string, required): Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'.

Output parameters:

- `result` (string)

### `compare_pricing` (~136 tokens)

Compare one pricing page at two dates: prices and plans on each, plus what was added/removed.

Input parameters:

- `date_a` (string, required): 'YYYY', 'YYYY-MM', 'YYYY-MM-DD' or 'latest'. The closest archived copy is used.
- `date_b` (string): 'YYYY', 'YYYY-MM', 'YYYY-MM-DD' or 'latest'. The closest archived copy is used.
- `response_format` (string): 'markdown' (default) or 'json'.
- `url` (string, required): Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'.

Output parameters:

- `result` (string)

### `compare_competitors` (~109 tokens)

Prices of 2-8 competitors' pricing pages side by side, as archived closest to the same date.

Input parameters:

- `date` (string): 'YYYY', 'YYYY-MM', 'YYYY-MM-DD' or 'latest'. The closest archived copy is used.
- `response_format` (string): 'markdown' (default) or 'json'.
- `urls` (array, required): 2-8 pricing pages, e.g. ['notion.so/pricing', 'coda.io/pricing'].

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/alialtunar-pricing-time-machine-mcp/pricing-time-machine-mcp#diagnostics

## Score history

- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 85
- 2026-10-28: 70
- 2026-10-27: 84
- 2026-10-26: 69
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 78
- 2026-10-13: 72
- 2026-10-12: 57
- 2026-10-04: 72
- 2026-10-03: 57
- 2026-10-02: 72
- 2026-10-01: 57

## Common questions

### What is the Pricing Time Machine MCP server?

Pricing Time Machine is an MCP server listed in the public MCP registry as io.github.alialtunar/pricing-time-machine-mcp. How any SaaS pricing page changed over the years, from the Wayback Machine. No API keys. This page covers its PyPI package (pricing-time-machine-mcp).

### Is the Pricing Time Machine MCP server safe to use?

Pricing Time Machine scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Pricing Time Machine MCP server expose?

Pricing Time Machine exposes 5 tools: pricing_snapshots, pricing_at, pricing_timeline, compare_pricing, compare_competitors. Their descriptions and schemas cost roughly 670 tokens of context every time the server is loaded.

### Is the Pricing Time Machine MCP server still maintained?

Pricing Time Machine is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Pricing Time Machine MCP server under?

Pricing Time Machine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/pricing-time-machine-mcp/
- Socket report: https://socket.dev/pypi/package/pricing-time-machine-mcp
- Repository: https://github.com/alialtunar/pricing-time-machine-mcp
- Changelog RSS feed: https://verifymcp.io/servers/alialtunar-pricing-time-machine-mcp/pricing-time-machine-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/alialtunar-pricing-time-machine-mcp/pricing-time-machine-mcp.json
- HTML version of this page: https://verifymcp.io/servers/alialtunar-pricing-time-machine-mcp/pricing-time-machine-mcp