Finance Tool Universe
Provides configured Google credentials for financial tools that call Google-backed external services, enabling authenticated provider access where supported by the tool catalog.
Enables Reddit access using configured credentials and an application user agent, supporting tools that collect or query Reddit data.
Enables Wikipedia access using the configured application user agent, supporting tools that query Wikipedia content.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Finance Tool Universe
One MCP service exposes 116 financial tools. All tools register through financial_tool.registry with one FastMCP manager, and their implementations live in financial_tool.tools. The tool catalog defines their public descriptions, schemas, examples, and functional groups. See the catalog guide for response conventions and tool-name mappings.
Get Started
Requires Python 3.10+. From the repository root, run:
python -m venv .venv
.venv/bin/python -m pip install -e .
cp config.example.yaml config.yaml
# Edit config.yaml with only the credentials and paths you need
chmod 600 config.yaml
.venv/bin/finance-tool-universe --check
.venv/bin/finance-tool-universeconfig.yaml is the user configuration file and is ignored by Git. Empty credential fields do not inherit keys from the environment. Local tools can run with the default configuration; tools that call external providers need the corresponding credentials.
Example MCP client configuration for stdio (replace <PROJECT_DIR> with the installation directory):
{
"mcpServers": {
"finance-tool-universe": {
"command": "<PROJECT_DIR>/.venv/bin/finance-tool-universe",
"env": {"FTU_CONFIG": "<PROJECT_DIR>/config.yaml"}
}
}
}FTU_CONFIG can point to another configuration file. Relative data paths resolve from that file's directory. Use --list-tools to list public tool names. Set server.transport: http to enable Streamable HTTP at http://<host>:<port>/mcp. Binding to a non-loopback address requires server.allowed_ips with client CIDR ranges. The default binds to 127.0.0.1. If you use a reverse proxy, enforce access control there; the service checks the directly connected IP.
For an A-share stock price, call market_data_get_akshare_stock_price with {"symbol":"600519.SH"} or a bare six-digit code. The result includes price, previous_close, daily price fields, volume, and retrieved_at. This AKShare snapshot depends on upstream availability and may be delayed; retrieved_at records collection time.
After installation via wheel, you can also run finance-tool-universe --init-config in the working directory to generate a configuration template.
Related MCP server: MCP Financial Data Gateway
Configuration fields
Location | Purpose |
| API credentials for FMP, FRED, Tavily, Google, Reddit, MinerU, and other providers; empty values mean unconfigured |
| Application identity for SEC, Wikipedia, and Reddit; use your own application name and contact address |
| Optional HTTP/HTTPS proxy; default is direct connection |
| Provider-facing IP settings; also configure any key restrictions in the provider's console |
| Client IP allowlist for MCP HTTP; unused by stdio |
| Directories for data, outputs, Qlib data, and optional training backend |
| Provider priorities, API URLs, and environment variable mappings |
| Service role permissions, caching, and rate limiting; |
For FMP and SEC access, set credentials.FMP_API_KEY and network.user_agent in config.yaml, then enable the relevant sources. Keep a configuration containing real credentials readable only by its owner, and do not add it to Git.
Optional tool dependencies
The core installation registers all 116 tools and supports local CSV/JSON-to-Parquet import. Some tools need optional SDKs, model libraries, or research projects when called:
.venv/bin/python -m pip install -e '.[qlib,crawlers,research,training]'The train_qcm, train_AFF, train_*_AlphaSAGE, and qlib_benchmark_runner tools launch external research projects configured under paths as background tasks. Each launch returns a task_id; poll it with training_get_task and list all tasks with training_list_tasks. Those projects, model weights, and market data are not bundled, so clone each project into the configured path (or set its FTU_*_REPO variable) before calling its trainer. See Training and backtesting below for a working setup. The former backtest tool is now backtest_model_predictions.
Training and backtesting — quick start
There are two kinds of training tools, and they need different setup.
1. train — self-contained, works out of the box
train runs a local scikit-learn RandomForest over a Qlib dataset or a prepared
Parquet file. No external repository is required.
# Install the Qlib extras in your environment
.venv/bin/python -m pip install -e '.[qlib]'Prepare input data one of two ways, then call train with a config file:
Option A — Qlib dataset. Download it first, then train against its handler:
// call tool: data_download
{"market": "cn", "provider_uri": "data/qlib/cn_data"}# configs/train.yaml
provider_uri: data/qlib/cn_data
region: cn
start_time: "2015-01-01"
end_time: "2019-12-31"
instruments: csi300
features: ["$close", "$open", "$high", "$low", "$volume"]
label: "Ref($close, -1)/$close - 1"
segments:
train: ["2015-01-01", "2019-12-31"]// call tool: train
{"config": "configs/train.yaml", "model_path": "output/model.pkl"}Option B — a pre-built Parquet with a (datetime, instrument) MultiIndex:
# configs/train.yaml
raw_parquet: data/features.parquet
feature_cols: ["open", "high", "low", "close", "volume"]
label_col: "next_return"// call tool: train
{"config": "configs/train.yaml", "model_path": "output/model.pkl"}train blocks until the model is saved to model_path.
2. train_qcm / train_AFF / train_*_AlphaSAGE — launchers for external projects
These run training scripts from three external research repositories that are not bundled and are not published here. They are launchers, not the training algorithms themselves: you must already have access to each project and clone it yourself.
Tool | Script it launches | Config key (default) | Override env var |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Clone each project you use into the default paths (substitute your repo URLs),
# then install each project's own dependencies as its README instructs.
mkdir -p external
git clone <your-alphaqcm-url> external/AlphaQCM
git clone <your-alphaforge-url> external/AlphaForge
git clone <your-alphasage-url> external/AlphaSAGEIf you keep the projects elsewhere, set the override variable instead of the
default path — for example export FTU_ALPHASAGE_REPO=/opt/research/AlphaSAGE.
Launching returns immediately with a task_id:
// call tool: train_gfn_AlphaSAGE
{"config_params": {"encoder_type": "gnn", "n_episodes": 10000}, "task_name": "gnn_run_1"}Then poll:
// call tool: training_get_task
{"task_id": "6f2e1b3a-9c41-4e72-9a11-8a3dd21cb004", "tail": 50}
// call tool: training_list_tasks
{}training_get_task reports one of running, completed, failed, or
not_found, along with the exit code, pid, error text, and recent log lines. If
a repository is missing, the launch tool raises a FileNotFoundError naming the
path to create and the FTU_*_REPO variable to set — it never leaves a silent
dangling task.
3. Qlib benchmark runners
qlib_benchmark_list_models scans the benchmark directory for workflow_config_*.yaml
files. qlib_benchmark_runner launches one through python -m qlib.cli.run:
.venv/bin/python -m pip install -e '.[qlib]'
git clone <your-qlib-benchmark-url> external/qlib_benchmark # or set FTU_QLIB_BENCHMARKS// call tool: qlib_benchmark_runner
{"yaml_path": "external/qlib_benchmark/benchmarks/XGBoost/workflow_config_xgboost_Alpha158.yaml",
"provider_uri": "data/qlib/cn_data",
"experiment_name": "xgboost_alpha158"}It returns a task_id; poll it with training_get_task as above.
4. Backtesting a trained model
Once you have a prediction file (a (datetime, instrument) MultiIndex CSV or
Parquet with a score and a label column), backtest_model_predictions writes
its Top-K portfolio metrics to backtest_metrics.json:
# configs/backtest.yaml
pred_path: predictions/pred.csv # or your .parquet
score_col: score
label_col: label
topk: 50
output: output// call tool: backtest_model_predictions
{"config": "configs/backtest.yaml"}The result file output/backtest_metrics.json contains cumulative and annual
return, annualized volatility, Sharpe ratio, and the number of periods.
Structure and validation
Path | Content |
| MCP entry point, configuration, and catalog loading |
| Unified implementation package for financial tools, connectors, and research algorithms |
| Registration functions and implementations for all 116 tools; optional dependencies loaded at call time |
| Metadata for 116 tools, groups, and name migrations |
| Data schemas and company aliases |
| Provider priorities and supported actions |
| Tool metadata, response conventions, and name mappings |
| Complete configuration template without actual credentials |
Provider column names and company aliases needed to match Chinese market data are stored with Unicode escapes. Public descriptions and display names are in English.
build/ is a temporary build output ignored by Git. Runtime code comes from src/ or the installed wheel.
The integration tests connect through MCP stdio, check the 116-tool registry, call representative local tools, and verify missing-credential errors. Run:
.venv/bin/python -m pip install -e '.[dev]'
.venv/bin/python -m pytest -qOpen source statement
The repository currently declares an MIT license. Confirm redistribution rights for included third-party modules before public release. external/ is not versioned. Keep credentials out of Git and rotate any credentials that appeared in earlier repository history.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
33 pay-per-call market and news data tools over MCP with free discovery and x402 payments.
Financial data and research MCP for US/CN/JP equities: filings, statements, ownership, signals.
Research-only MCP server: your AI as a quant research desk. 90 tools, no trades, no brokers.
One API and MCP server for financial and economic data: markets, economics, companies and more.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables querying real-time and historical financial market data for stocks, options, forex, and crypto, including quotes, trades, technical indicators, and reference data through a set of MCP tools.713MIT
- AlicenseNot gradedqualityDmaintenanceProvides 10 financial data tools (market data, economic indicators, news, insider trades, and calendars) via a single MCP layer, enabling any MCP-compatible LLM to access diverse financial data through a unified interface.1MIT

inferventisofficial
FlicenseNot gradedqualityCmaintenanceEnables AI agents to access real-time financial data, news, and web reading through a single MCP endpoint with zero installation.-- FlicenseNot gradedqualityAmaintenanceEnables AI agents and backend workflows to access standardized multi-market financial data, technical indicators, fundamentals, news, filings, money flow, and CSV/JSON exports through MCP tools and HTTP endpoints.-