Skip to main content

Vintage — point-in-time research terminal

A research terminal that costs $0 and won't lie to you about your Sharpe.

PyPI CI License Python

A Claude session: install Vintage, backtest three signals, watch the deflated Sharpe collapse to 0.09

rezasoleymanifar.github.io/vintage


Free financial data exists and is scattered across twenty APIs with twenty shapes. Everyone rebuilds the same glue, badly, and quietly ends up backtesting on restated figures and survivor-only universes.

Vintage is that glue, written once, served over MCP. It hosts no data — it connects, normalizes, and preserves vintage.

Install

One line. Nothing to clone.

Claude Code

claude mcp add vintage -s user -- uvx vintage-mcp

Claude Desktop / any MCP client — add to your config file:

{
  "mcpServers": {
    "vintage": {
      "command": "uvx",
      "args": ["vintage-mcp"]
    }
  }
}

Claude Desktop config lives at %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS). Restart the app afterwards — MCP servers load once at startup.

Needs uv. If you'd rather use pip: pip install vintage-mcp and set the command to vintage.

Optional configuration

Everything works with zero configuration. These make it work better:

Variable Why
VINTAGE_USER_AGENT SEC EDGAR asks for a real contact. "Your Name your@email.com".
FRED_API_KEY Free key — unlocks 800k macro series with first-release vintages.
VINTAGE_CACHE_DIR Defaults to ~/.cache/vintage.

Set them under "env" in the same config block:

{
  "mcpServers": {
    "vintage": {
      "command": "uvx",
      "args": ["vintage-mcp"],
      "env": {
        "VINTAGE_USER_AGENT": "Jane Quant jane@example.com",
        "FRED_API_KEY": "..."
      }
    }
  }
}

Your key stays in this file. It is read by the server process and is never passed through the model or written into the conversation.

Try it

Once installed, ask your assistant:

"What was Apple's total assets as of January 2020 — and has it been restated since?"

"Backtest 12-1 momentum on the Dow 30 since 2010."

"Now try short-term reversal instead. Did the alpha survive?"

The third question is the one that matters. Watch the deflated Sharpe fall as you keep asking.

The two dates

Every value carries both:

  • observed_at — what period the number describes
  • known_at — when it first became public

A backtest may only use rows whose known_at precedes the trade date. That is structural, not a setting: the panel is indexed on known_at, so any slice of it is automatically point-in-time. There is no flag to turn it off.

Sources that cannot supply an honest known_at are flagged UNKNOWN_VINTAGE rather than given a fabricated date.

Six ways yesterday's data quietly changed

  • Lag — the number is true in December, published in February.
  • Restatement — the company says "oops, wrong" and changes last year's figure.
  • Revision — the government keeps fixing old jobs and inflation numbers, for years.
  • Survivorship — dead companies get deleted; only the winners are still listed.
  • Membership — today's S&P 500 list is not the list from 2005.
  • Price adjustment — splits and dividends silently rewrite every price before them.

All six say the same thing: the data you have today is not what people saw back then.

Six verbs

Source is a parameter, never a separate tool. Twenty more sources adds zero tools.

Verb Does
resolve Any identifier → the entity key everything else accepts
discover Plain-English search across every source's catalog
fetch The workhorse. Any field, any source, with as_of
events Filing timeline with exact public timestamps
backtest Cross-sectional signal → returns, costs, honesty report
benchmark Your returns → correlation and alpha vs published factors

Plus status for cache size, keys, and how many specs you have tried.

The honesty engine

A conversational backtester is an overfitting machine unless it counts how many times you asked. Every backtest returns:

  • Deflated Sharpe (Bailey & López de Prado, 2014) accounting for every spec tried this session
  • The Sharpe noise would have produced given that trial count
  • First-half vs second-half Sharpe
  • Costs always charged on turnover — there is no zero-cost mode
  • A standing survivorship warning until point-in-time universes land

This is the part a paid terminal does not do for you.

The method

Vintage implements the backtest-validation literature rather than inventing its own statistics. Execution realism is a different problem, already solved by LEAN and Nautilus Trader — Vintage runs before that, at the stage where most ideas should die.

Technique Source Status
Point-in-time panel indexed on known_at structural, no flag to disable ✅ shipped
Costs charged on turnover, always no zero-cost mode exists ✅ shipped
Deflated Sharpe Ratio Bailey & López de Prado (2014) ✅ shipped
Session trial ledger feeding the deflation Bailey & López de Prado (2014) ✅ shipped
Probability of Backtest Overfitting, via CSCV Bailey, Borwein, López de Prado & Zhu (2017) ⏳ planned
Purged k-fold CV with embargo Advances in Financial Machine Learning, ch. 7 ⏳ planned
Combinatorial purged cross-validation Advances in Financial Machine Learning, ch. 12 ⏳ planned
Minimum Backtest Length Bailey, Borwein, López de Prado & Zhu (2014) ⏳ planned
Newey–West adjustment for autocorrelated returns Newey & West (1987) ⏳ planned
Square-root market impact Almgren et al. (2005) ⏳ planned

Citations are references, not endorsements — none of these authors is affiliated with Vintage. Anything marked planned is not in the code yet, and the backtest response says so at runtime rather than in the footnotes.

Where the data comes from

10,398
ticker-mapped US filers
800k+
macro series with vintages
500+
XBRL fields per large filer
0
API keys required
$0
forever

Three of the five are the primary source — not a reseller, not a scraper. The filings come from the regulator that receives them, the macro series from the central bank that publishes them, and the factors from the university that computes them.

Source Standing Covers Key Point-in-time
SEC EDGAR XBRL Primary · US regulator Every concept every US filer has tagged, with accession number and filing date on each figure. Restatements arrive as rows, never as an overwrite. none ✅ native filing dates
SEC filings stream Primary · US regulator 8-K, 10-K, 10-Q, Form 4, 13D/G — timestamped to the second EDGAR accepted them. none ✅ exact timestamps
FRED / ALFRED Primary · central bank Federal Reserve Bank of St. Louis. ALFRED keeps first releases, so you can ask what CPI looked like that morning. free ✅ first-release vintages
Ken French Data Library Primary · academic Dartmouth. FF3, FF5, momentum, daily FF3, 49 industry portfolios — from where the authors publish them. none ❌ rebuilt each release
Yahoo Finance Third party Daily OHLCV and adjusted close, decades deep. none ⚠️ adjusted retroactively, flagged on every row

Counts current as of August 2026. Vintage redistributes none of this — each upstream source keeps its own terms.

Stooq was the intended price spine — friendlier terms — but it now gates programmatic access behind a JavaScript check. The adapter stays in case that lifts.

See DATA_SOURCES.md for the full free-data landscape and DESIGN.md for the architecture.

Cache

Gzipped JSON in ~/.cache/vintage, tiered by how mutable the data is: closed periods never refetch, academic datasets monthly, current fundamentals daily, prices per session. An hour of conversation is roughly 20 upstream calls.

Known gaps

Stated plainly, because the alternative is shipping a bad substitute:

Data:

  • Survivorship — universes are current-listing only. Form 25 delistings are the next build and the backtester warns until then.
  • Analyst estimates — no free source exists.
  • Historical options chains — paid everywhere.
  • Point-in-time index membership — licensed by S&P and MSCI.

Engine — the backtester is vectorized and cross-sectional, which is a rung below an event-driven simulator:

  • No purging or embargo — overlapping label windows can leak across a train/test split (López de Prado, AFML ch. 7). Deflation catches selection bias, not leakage.
  • No market impact — costs are a flat charge on turnover, so large-notional results are optimistic.
  • No PBO — deflated Sharpe covers multiple testing; the Probability of Backtest Overfitting via combinatorially symmetric cross-validation would be the stronger test.
  • Trial count resets each session — ask forty things today and forty tomorrow, and tomorrow starts from zero.
  • Sharpe is per observation, not annualized — that is the frequency the deflation is defined at, and the response says so.

Development

git clone https://github.com/RezaSoleymanifar/vintage
cd vintage
uv sync --group dev
uv run pytest

smoke_test.py exercises all six verbs against the live sources — useful before a release, and it needs network.

License

MIT. Vintage redistributes no data; each upstream source keeps its own terms.

mcp-name: io.github.rezasoleymanifar/vintage

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

vintage_mcp-0.1.0.tar.gz (485.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

vintage_mcp-0.1.0-py3-none-any.whl (35.4 kB view details)

Uploaded Python 3

File details

Details for the file vintage_mcp-0.1.0.tar.gz.

File metadata

  • Download URL: vintage_mcp-0.1.0.tar.gz
  • Upload date:
  • Size: 485.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for vintage_mcp-0.1.0.tar.gz
Algorithm Hash digest
SHA256 306afae5f9122f142c2b2a154b199d8ac199fc570d6a8f4d6069e1b15570aa08
MD5 6caa418decf8b8d371d12a83bc339ccd
BLAKE2b-256 22b5c48905f46c33c094b0b15d7cf83f3303eb40b8aa2b97f651032fefdcdb47

See more details on using hashes here.

Provenance

The following attestation bundles were made for vintage_mcp-0.1.0.tar.gz:

Publisher: release.yml on RezaSoleymanifar/vintage

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file vintage_mcp-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: vintage_mcp-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 35.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for vintage_mcp-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 178459b52dea6dd6e49d433dcf66809f5202f5c096223d83b934dfa8c502f99e
MD5 51447a40944d63f79839fafb646996b6
BLAKE2b-256 556d435a79f71be40206e8fbebe7598e6bc7ac148abb83c7c568f5ad7ecd9d3e

See more details on using hashes here.

Provenance

The following attestation bundles were made for vintage_mcp-0.1.0-py3-none-any.whl:

Publisher: release.yml on RezaSoleymanifar/vintage

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page