Flox MCP vs Tradesearcher Agent Tools MCP
A side-by-side look at the Flox MCP and Tradesearcher Agent Tools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Flox MCP for finance & fintech work as a local process; choose Tradesearcher Agent Tools MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Flox MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list_indicators, lookup_error_code, list_capi_functions.
Choose Tradesearcher Agent Tools MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRADESEARCHER_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 65/100 · Great | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | TRADESEARCHER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 228 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Flox MCP | View Tradesearcher Agent Tools MCP |
Tools & capabilities
Flox MCP tools 13
list_indicatorsEvery indicator in `lrvx` with class signature, batch fn (if any), and shape. Filter by substring.lookup_error_codeE_SYM_001` → full Markdown page with fix recipe, common causes, diagnostics.list_capi_functionsSearch the lrvx C-API surface from the committed ABI snapshot. Returns `name + return type + parameter types`.validate_strategyStatic-analysis check on Python strategy code: AST parses, expected hooks present, no `eval`/`exec`.explain_eventDescribe the fields of a lrvx event struct (`LrvxTradeData`, `LrvxBookData`, `LrvxBarData`, `LrvxSymbolContext`, `LrvxSignal`). Accepts a struct name or a raw event dict.lookup_symbolTake any binding-local spelling (`LrvxBarData`, `BarData`, `lrvx_indicator_ema`, `ema`) and return what the symbol is called in C-API, Python, Node, and Codon.list_bindingsEnumerate the exports of one binding (capi, python, node, codon, quickjs). Substring filter and limit.get_exampleCode from `docs/examples/` matching a topic (strategy, connector, indicator, event-handler, risk, backtest), optionally filtered by language.scaffold_strategyStarter strategy class for Python or Node. Three kinds: bar-driven, trade-driven, hybrid. The Python output goes through `ast.parse` + `validate_strategy`; the Node output goes through `node --check`. CI fails if either breaks, so templates can't quietly rot.docs_searchTop-k FTS5 search over the docs. The index is built from an allowlist of roots; private trackers and `CLAUDE.md` are not in that allowlist.run_backtestRun a Python strategy against a CSV dataset in a sandboxed subprocess. Caps CPU, memory, and output size; wall-clock timeout. **MVP sandbox** — caps resources but does not isolate filesystem or network. Treat the same way as any untrusted Python; use nsjail / firejail / Docker for production.compute_indicatorRun one lrvx indicator over a list of floats. Accepts class-form (`EMA`) or function-form (`ema`) names and forwards extra kwargs to the constructor. Input capped at 1 MiB. Needs `lrvx` installed (`pip install "lrvx-mcp[lrvx]"`).- +1 more on the listing page
Tradesearcher Agent Tools MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Flox MCP
{
"mcpServers": {
"flox-foundation-flox-mcp": {
"command": "uvx",
"args": [
"lrvx-mcp"
]
}
}
}
Tradesearcher Agent Tools MCP
{
"mcpServers": {
"mcp-server-4": {
"command": "npx",
"args": [
"-y",
"@tradesearcher/mcp-server"
],
"env": {
"TRADESEARCHER_API_KEY": "YOUR_TRADESEARCHER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Flox MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Tradesearcher Agent Tools MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Flox MCP for finance & fintech work and Tradesearcher Agent Tools MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Flox MCP is listed as free. Auth: no auth required. Tradesearcher Agent Tools MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add flox-foundation-flox-mcp and mcp-server-4 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Flox MCP has a quality signal of 65/100 (Great) with 5 views, 0 installs and 228 GitHub stars. Tradesearcher Agent Tools MCP has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.