No user-submitted related servers found.
Scored across 70 tools
Most tools have clearly distinct purposes and the namespace prefixes (memory_, paywall_, identity_, broker_sync_, protocol_health_, registry_, reputation_) sharply separate the sub-domains. A few overlaps exist—e.g. orderbook vs kalshi_market (which bundles an orderbook), price vs ohlcv, market_overview vs market_clock, and reputation_status vs reputation_statement—but descriptions disambiguate them. Overall selection is reasonably unambiguous despite the large surface.
The bulk of the server uses a consistent prefix_verb_noun pattern (memory_store, paywall_create_route, broker_sync_register_user, identity_get_nonce), and prefixes are stable per sub-service. However, the entire Trading Data group breaks convention with bare nouns lacking any verb or prefix (sentiment, price, orderbook, gas, fvg, atr), producing a mixed set of conventions across the server. Still readable but inconsistent.
At 70 tools this is far beyond the well-scoped 3-15 range and sits in the 'too many' tier. Although it aggregates roughly ten distinct sub-services (each individually coherent), the raw volume makes the overall set heavy and hard to reason about as a unit.
Coverage is strong across most sub-domains: Memory offers full CRUD plus history, update-versioning and deletion audit; Paywall has complete route lifecycle (create/import/update/delete/list/settlements); Identity, Registry, Reputation and Broker Sync each cover their core lifecycle. Minor gaps exist (e.g. no broker disconnect/delete, limited write ops on some oracles), but the surface is broadly complete for its stated purposes.