get_tickers

2 registry entries were observed exposing a tool named get_tickers — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,548 of 40,914 scannable entries (31%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @pexbot/mcpMCPcommunitytrust 60/100 · B

   v3.0.0

   ↓ 44/wk

   ★ 1

   MCP server for pex.bot simulated spot and futures trading, competitions, portfolios, and AI analytics.

   ClaudeCursorCopilotGemini

   mikusnuzMIT1mo agonpmGitHub+compareobserved 2026-09-02 · static extraction

   mcpmcp-servermodel-context-protocolpexbotcryptotrading
2. io.github.luziadev/luziaMCPcommunitydegradedtrust 60/100 · B

   v1.3.0

   Real-time crypto prices from Binance, Coinbase, Kraken, OKX, and Bybit

   ClaudeCursorCopilotChatGPTGemini

   io.github.luziadevUnknown6mo agonpmGitHub+compareobserved 2026-06-13 · static extraction

   mcp

All indexed toolsSearch the registry for get_tickers