Vintage
PYPI · VINTAGE-MCP
Free financial data from eleven sources behind six verbs, point-in-time where the source allows.
Available components
Last scanned (1 day ago)
Scores higher than 94% 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 Security100
- No malware found by supply-chain analysis.Pass
- 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 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to RezaSoleymanifar/vintage). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 89 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 997 tokens (~142/item across 7 items; 7 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- Package version: 0.4.0 → 0.9.0 functional
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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/vintage-mcp@0.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | RezaSoleymanifar/vintage |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/RezaSoleymanifar/vintage/.github/workflows/release.yml@refs/tags/v0.9.0 |
| Rekor log index | 2362622792 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d7ed3ad62d142faaf7003cff349044bdb177feb1db5d18aeb77b988131094a02 |
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 35 packages
| Packages resolved | 35 |
|---|---|
| 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 →
backtest ~183
Run a cross-sectional backtest. Point-in-time and costed by construction. At each rebalance the engine sees only data knowable strictly before that date. Costs are always charged on turnover; there is no zero-cost mode. The result includes a deflated Sharpe that accounts for how many specs have been tried this session. Always report it alongside the raw Sharpe — a conversational backtester is an overfitting machine without it. Signals: momentum_12_1, momentum_6_1, reversal_1m, low_volatility, trend_200d.
| Name | Type | Req | Description |
|---|---|---|---|
| cost_bps | number | – | – |
| end | – | – | – |
| long_pct | number | – | – |
| rebalance | string | – | – |
| short_pct | number | – | – |
| signal | string | – | – |
| start | – | – | – |
| universe | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
benchmark ~83
Score a backtest against the published Fama-French factors. Answers the question that decides whether a result is interesting: did you discover something, or rebuild a factor that has been public since 1993? Datasets: ff3, ff5, momentum, ff3_daily, industry49.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | – |
| run_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
discover ~85
Search every source's catalog for fields matching a plain-English query. This is how breadth is reached — there is no per-source tool. With `entity` set, it also searches that company's reported XBRL concepts, which is the reliable way to find the exact field name for fundamentals.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
events ~91
Timeline of what happened to an entity, with exact public timestamps. Currently the SEC filing stream — 8-K material events, 10-K/10-Q, Form 4 insider transactions, 13D/G stakes. Every row carries the minute it became public, which is what makes event studies possible.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| entity | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fetch ~272
Fetch any field from any source, as point-in-time rows. Field forms: "us-gaap:Assets" (needs entity), "price:close" (needs entity), "fred:CPIAUCSL", "french:ff3", "openap:Mom12m" (or "openap:*" for all 331 published claims), "crypto:close" (needs an entity like BTC-USD), "short:short_ratio" (needs an entity), "ape:all-stocks", "13f:value" (needs a manager like BERKSHIRE), "bls:CUUR0000SA0", "bea:T10101". Run discover first if unsure. `as_of` is the point-in-time switch: it drops every row that was not public on that date, so you see what a researcher on that day saw, restatements and all. `quarter` picks a reporting period for 13F holdings ("2024-12-31" or "2024"); without it you get the latest.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| end | – | – | – |
| entity | – | – | – |
| field | string | yes | – |
| form | – | – | – |
| limit | integer | – | – |
| quarter | – | – | – |
| start | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve ~74
Turn any identifier into the entity key every other verb accepts. Accepts a ticker ("AAPL"), a CIK ("CIK0000320193" or "320193"), a FRED series id, or a French dataset name. Start here when unsure what an entity is called.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
status ~22
Cache size, configured keys, sources available, and specs tried so far.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Vintage MCP server?
Vintage runs locally as a PyPI package, launched with uvx vintage-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 · vintage-mcp
claude mcp add rezasoleymanifar-vintage -- uvx vintage-mcp
What is the Vintage MCP server?
Vintage is an MCP server listed in the public MCP registry as io.github.RezaSoleymanifar/vintage. Free financial data from eleven sources behind six verbs, point-in-time where the source allows. This page covers its PyPI package (vintage-mcp).
Is the Vintage MCP server safe to use?
Vintage scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Vintage MCP server expose?
Vintage exposes 7 tools: resolve, discover, fetch, events, backtest, and 2 more. Their descriptions and schemas cost roughly 810 tokens of context every time the server is loaded.
Is the Vintage MCP server still maintained?
Vintage 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 Vintage MCP server under?
Vintage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.