Skills/PyPI/vintage-mcp

vintage-mcp@0.9.0

VERIFIED· not started

Publisher claims: "A research terminal that costs $0 and won't lie to you about your Sharpe — point-in-time financial data over MCP" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher rezasoleymanifar · publishing for 106 daysInstalls 162Last detonated 11 min ago
$claude mcp add vintage-mcp -- uvx vintage-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
BEA_API_KEYBLS_API_KEYFRED_API_KEYConfiguration, not credentials: VINTAGE_CACHE_DIR, VINTAGE_USER_AGENT
Where it talks to
no vendor host named in the codeAlso sec.gov, yahoo.com, stlouisfed.org, apewisdom.io, bea.gov, bls.gov, cboe.com, cftc.gov, coinbase.com, europa.eu, finra.org, dartmouth.edu, githubusercontent.com, openassetpricing.com, stooq.com, treasury.gov, quantconnect.com, nautilustrader.io, astral.sh — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names sec.gov, yahoo.com, stlouisfed.org, apewisdom.io, bea.gov, bls.gov, cboe.com, cftc.gov, coinbase.com, europa.eu, finra.org, dartmouth.edu, githubusercontent.com, openassetpricing.com, stooq.com, treasury.gov, quantconnect.com, nautilustrader.io, astral.sh as well as its own vendor. The guard injects BEA_API_KEY, BLS_API_KEY, FRED_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx vintage-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
Process kill commandtools/build_coverage.py:104 · Process kill command — agent can terminate processesexcept Exception as exc: # a dead upstream should not kill the docFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
File permission modification command.github/workflows/release.yml:93 · File permission modification command — agent changes file ownership/permissionschmod +x mcp-publisherFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈64 tok
1 file · 64 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.