trackr
Related Servers
Alternatives to trackr
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server exposing StoneX Client REST API endpoints as tools, enabling account balances, positions, activity, and performance retrieval via natural language. Requires a user-supplied access token or session cookie.2 npm2MIT
- AlicenseAqualityCmaintenanceEnables fetching poker sessions and computing aggregate statistics (profit, win rate, etc.) from the Poker Bankroll Tracker API.216 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides access to the UK FCA Financial Services Register, enabling firm and individual searches, firm details by FRN, appointed representatives lookups, and individual records by IRN.248 npmMIT
- AlicenseAqualityBmaintenanceProvides read-only access to App Store Connect analytics, sales, finance, and customer review data, with tools to fetch and parse reports from Apple's Analytics Reports API and other report endpoints.14Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides login-gated access to FindData's crawled business data, enabling users to read indicators over time, list concepts, search via natural language, and run graph queries.MIT
- AlicenseNot gradedqualityAmaintenanceEnables reading a Trading 212 Stocks ISA and safely previewing, approving, placing, and cancelling orders, with account, position, order-history, and instrument-search tools.MIT
TDQS
Scored across 3 tools
Each tool maps to a single, clearly distinct session operation: authenticate (login), inspect/change the active firm (switch_firm), and clear credentials (logout). There is no realistic scenario where an agent could confuse these three actions.
All names are lowercase snake_case and verb-oriented (login, switch_firm, logout), so the pattern is readable and predictable. The only minor deviation is that login/logout are bare verbs while switch_firm uses verb_noun, but the convention is still coherent.
Three tools is small, but it is well matched to a narrow session/authentication scope where each tool earns its place. It would be thin only if the server were expected to expose broader ForexTrackr data operations, which the surface does not claim.
The full credential lifecycle is covered: authenticate, switch between firms (which also reports the active firm, avoiding a separate list tool), and forget credentials. Minor gaps are the absence of a standalone status/whoami check and any key-refresh or multi-key management operation, but agents can work around these via switch_firm.