Vintage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRED_API_KEY | No | Free API key from FRED to unlock 800k macro series with first-release vintages. | |
| VINTAGE_CACHE_DIR | No | Directory for cache. Defaults to ~/.cache/vintage. | ~/.cache/vintage |
| VINTAGE_USER_AGENT | No | User agent string for SEC EDGAR. Example: "Your Name your@email.com". |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capabilitiesA | Everything Vintage can answer, with the arguments each field needs. Call this first. It returns every field prefix, whether it needs an
|
| resolveA | 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. |
| discoverA | 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
|
| fetchA | 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.
|
| eventsA | 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. |
| backtestA | 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 Signals: momentum_12_1, momentum_6_1, reversal_1m, low_volatility, trend_200d. |
| benchmarkA | 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. |
| statusA | Cache size, configured keys, sources available, and specs tried so far. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| capabilities_resource | The same surface as the `capabilities` tool, for clients that preload resources instead of spending a tool call on orientation. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RezaSoleymanifar/vintage'
If you have feedback or need assistance with the MCP directory API, please join our Discord server