Finance Toolkit vs Financial Evidence
A side-by-side look at the Finance Toolkit and Financial Evidence MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Finance Toolkit for finance & fintech work as a local process; choose Financial Evidence for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Finance Toolkit when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
Choose Financial Evidence when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
financial_evidence_topics, financial_evidence_route, financial_evidence_fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 49/100 · Fair | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 5,446 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Finance Toolkit | View Financial Evidence |
Tools & capabilities
Finance Toolkit tools
No tool names declared yet. Check the project README from the listing page.
Financial Evidence tools 3
financial_evidence_topicsList supported topics and their fixed public raw-JSON routes without network access.financial_evidence_routeResolve one or more financial research topics to fixed public raw-JSON sources without fetching them.financial_evidence_fetchFetch bounded untrusted read-only JSON from fixed LiquiLens, Undertow, Seiche, and Palimpsest routes. Status reports transport only; evidence is not evaluated and Evidence Carrier verification is not performed.
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.
Finance Toolkit
{
"mcpServers": {
"finance-toolkit": {
"command": "uvx",
"args": [
"financetoolkit"
]
}
}
}
Financial Evidence
{
"mcpServers": {
"financial-evidence": {
"command": "uvx",
"args": [
"financial-evidence"
]
}
}
}
Frequently asked questions
Finance Toolkit is categorized under Finance & Fintech and uses a local stdio subprocess. Financial Evidence belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Finance Toolkit for finance & fintech work and Financial Evidence 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.
Finance Toolkit is listed as free. Financial Evidence is listed as free. Auth: no auth required. 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 finance-toolkit and financial-evidence as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Finance Toolkit has a quality signal of 49/100 (Fair) with 4 views, 0 installs and 5,446 GitHub stars. Financial Evidence has 79/100 (Great) with 3 views, 0 installs and 1 GitHub stars.