financial-evidence
Related Servers
Alternatives to financial-evidence
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides web search, page fetching, and A-stock data access (financial reports, announcements, research reports, penalties, IR meetings) via MCP tools.-
- FlicenseAqualityCmaintenanceProvides read-only MCP tools to search and retrieve evidence-grounded knowledge compiled from video content, including hybrid semantic and lexical search with citations.5-
- AlicenseNot gradedqualityBmaintenanceProvides access to Hong Kong Monetary Authority public open data via MCP, enabling natural language queries without an API key.364 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query live pricing, resale, company KYC, SEC filings, patents, trademarks, public tenders, auctions and related market intelligence through MCP, returning clean typed JSON from primary sources on a pay-per-result basis.MIT

LuxAlgo Library MCPofficial
AlicenseAqualityAmaintenanceRead-only, keyless MCP server for searching and retrieving trading concepts, indicator details, families, and source code from the LuxAlgo Library.48159 npm82MIT- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to ask plain-language questions and receive answers grounded only in documents the configured role is cleared to read, with the same access-controlled tools available across any client.-
TDQS
Scored across 3 tools
The fetch tool is clearly distinct, but topics and route overlap somewhat since topics already lists the raw-JSON routes. The distinction is mostly clear: topics returns the full catalog, while route resolves a specific topic to its sources.
All tool names share the consistent financial_evidence_ prefix and use straightforward lowercase snake_case. The final words topics, route, and fetch are simple and predictable.
Three tools is well-scoped for the stated purpose of listing, resolving, and fetching financial evidence sources. Each tool serves a distinct step in the workflow without unnecessary bloat.
The topics -> route -> fetch pipeline is complete for transport-level evidence retrieval. Missing verification or evaluation is intentional and explicitly disclaimed, but the server name might lead agents to expect some evidence assessment capability.