My Quant — Editorial Discovery
Related Servers
Alternatives to My Quant — Editorial Discovery
- AlicenseAqualityAmaintenancePublic MCP research for AI finance and trading agents: funding, bank risk and liquidity evidence. Companion SDK: persistent Python MCP sessions and Python/JS source-status streams. Setup: https://beepboop2025.github.io/financial-evidence-skills/distribution/ai-trading-tools.html. No data API key. Keep source dates, rights and gaps. No live quotes or execution.231MIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceAggregate, route, and orchestrate multiple MCP backend servers behind a single MCP endpoint.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to resolve, inspect, acquire, verify, and query routes, capabilities, schema, and health for public and authorized web resources, with fail-closed statuses and artifact production.MIT
- AlicenseNot gradedqualityCmaintenanceCentralized MCP control plane that proxies multiple upstream MCP servers with tool namespacing, filtering, policy enforcement, audit logging, and health checks.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP clients with a searchable registry of MCP servers, enabling discovery and publishing of servers.42 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables clients to connect once and access the union of multiple backend MCP servers' tools through a single unified interface, with namespaced tool routing, capability search, and health isolation.MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.18MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct capability: metadata discovery (list_capabilities), health/version diagnosis (get_health), chronological listing (latest_stories), exact-ID retrieval (get_story), and text search (search_stories). The descriptions explicitly cross-reference sibling tools ('Use search_stories for...', 'Use get_story for an exact ID'), removing ambiguity between the two metadata tools and between listing vs. searching. An agent can reliably select the right tool for a given intent.
Most tools follow a predictable verb_noun snake_case pattern (list_capabilities, get_health, get_story, search_stories). The outlier is latest_stories, an adjective_noun phrase with no verb, which slightly breaks the pattern. Otherwise the convention is consistent and readable.
Five tools is well-scoped for a read-only editorial discovery surface, with each tool earning its place (capabilities, health, list, get, search). No redundant or trivially thin endpoints, and no bloat. The set is tight and purposeful.
The surface covers the core read-only discovery lifecycle: discover capabilities, verify health, list recent stories, fetch by ID, and search by text. Minor gaps remain, such as no pagination beyond 20 records and no tag/beat browsing distinct from free-text search, but agents can work around these. Coverage is solid for the stated public, read-only purpose.