financial-evidence
Related Servers
Alternatives to financial-evidence
- AlicenseAqualityBmaintenanceGive AI agents cited funding, money-market, FX and capital-market evidence through 16 public MCP tools. Keep source dates, freshness checks and coverage gaps attached; China macro coverage is metadata-only. No API key is required for the public surface. Research context only; no trade execution.2162AGPL 3.0
Related Servers
- AlicenseAqualityCmaintenanceExposes public marketplace data — offerings, screening and comparison, news, sponsor listings, and platform reference text — as typed read-only tools any MCP-compatible agent can call without an API key or account. Every response carries provenance, honest nulls for undisclosed values, and a standing disclaimer, and no registered tool can write or transact by default.9Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides web search, page fetching, and A-stock data access (financial reports, announcements, research reports, penalties, IR meetings) via MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language research and analysis across public filings, earnings calls, financial metrics, stock and crypto data, news, and prediction markets with structured, source-backed answers in MCP clients.-
- AlicenseNot gradedqualityCmaintenanceEnables users to run deep research, quick searches, and report writing, and to retrieve research sources and context through MCP-compatible clients.MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language financial research across SEC filings, earnings transcripts, financial metrics, stock and crypto market data, stock news, and prediction markets, returning structured, source-backed answers within MCP clients.-
- FlicenseNot gradedqualityBmaintenanceEnables any MCP client to anonymously query listed API prices across official, inference, and relay providers, find free credits and promotions, resolve model names, and retrieve quote evidence and glossary information without an API key.1,412-
TDQS
Scored across 3 tools
fetch is clearly distinct (it actually retrieves data), but topics and route both return topic-to-route mappings without fetching, differing only in all-vs-subset scope. An agent could plausibly misselect between them, though the descriptions do help.
All tools use the consistent financial_evidence_ snake_case prefix. Minor deviation: fetch and route are verbs while topics is a noun, but the pattern is still predictable.
Three tools is on the lean side but reasonable for this narrow, read-only domain (discover topics, resolve routes, fetch JSON). Each tool roughly earns its place, though route and topics could arguably merge.
The discover-resolve-fetch workflow covers the stated read-only purpose with no obvious dead ends. Evaluation/verification is explicitly out of scope, so this is a minor scope limitation rather than a surface gap.