Pricing Time Machine
PYPI · PRICING-TIME-MACHINE-MCP
How any SaaS pricing page changed over the years, from the Wayback Machine. No API keys.
Available components
Last scanned (21 hours ago)
Scores higher than 67% of PyPI servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 +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.
- 21 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/pricing-time-machine-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_competitors ~109
Prices of 2-8 competitors' pricing pages side by side, as archived closest to the same date.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 2-8 pricing pages, e.g. ['notion.so/pricing', 'coda.io/pricing']. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compare_pricing ~136
Compare one pricing page at two dates: prices and plans on each, plus what was added/removed.
| Name | Type | Req | Description |
|---|---|---|---|
| date_a | string | yes | '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 | yes | Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pricing_at ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pricing_snapshots ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pricing_timeline ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Pricing page, e.g. 'notion.so/pricing' or 'https://slack.com/pricing'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
pypi · pricing-time-machine-mcp
claude mcp add alialtunar-pricing-time-machine-mcp -- uvx pricing-time-machine-mcp
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.