@hashpower/mcp
OfficialRelated Servers
Alternatives to @hashpower/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to inspect brokerage data through read-only Zerodha Kite and Alpaca adapters and exercise order lifecycle workflows in a local synthetic paper sandbox for Indian and US cash equities.14MIT
- FlicenseAqualityCmaintenanceEnables agents to generate alpha signals, retrieve market snapshots, compute portfolio risk, validate and submit paper orders, and trigger a kill switch, all under deterministic pre-trade risk controls and audit logging.5-
- AlicenseAqualityBmaintenanceEnables AI agents to paper-trade on Polymarket against live order books with realistic fees and fill mechanics, including market search, portfolio tracking, and strategy backtesting.33157 PyPI509MIT
- AlicenseNot gradedqualityBmaintenanceProvides a safe paper-trading twin of the Binance Agent OS MCP API so agents can be rehearsed, scored, gated for go-live, and shadow-compared against live calls without using real funds.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to trade crypto with paper money, access market data, view leaderboards, and manage trading bots via an MCP-compatible interface.16MIT

bactory-mcpofficial
AlicenseAqualityBmaintenanceProvides AI assistants with live Base market data and Chainlink oracle freshness, and simulates AgentGuard checks so users can analyze markets and verify whether proposed treasury actions would execute.12MIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource or action: market rules, margin model, units/scaling, and deployments are clearly separated, while check_can_place_order, simulate_order, and build_order_tx form a clear pre-trade pipeline. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tool names follow a consistent snake_case verb_noun pattern: read-only operations use get_, and simulation/build operations use descriptive verbs. The naming style is uniform and predictable across the entire toolset.
12 tools is a well-scoped count for a trading-domain MCP server. Each tool covers a distinct aspect—market data, account state, margin checks, simulation, and transaction building—without redundancy or bloat.
The toolset covers the core domain well: market semantics, live data, positions, margin status, order pre-flight checks, and unsigned transaction building. Obvious lifecycle operations like cancel or withdraw are not exposed, but the explicit prototype-only and external-encoding caveats make this a minor gap rather than a severe one.