bybit-trading (Vanszs/Bybit_AutoTrade) is an MCP server listed on the M8ven Trust Index. It scores 73 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

C
Limited view
73/100
2 months ago

bybit-trading

MCP server for cryptocurrency trading across multiple exchanges (Bybit, Binance, KuCoin, etc.) with real-time price data, comparison, and natural language query support. Integrates with AI assistants via the Model Context Protocol.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Vanszs

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 5 credentials: TELEGRAM_BOT_TOKEN, ZAI_API_KEY, BYBIT_API_KEY, BYBIT_API_SECRET, BOT_AUTH_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretTELEGRAM_BOT_TOKENyour_telegram_bot_token_here
🔐 secretZAI_API_KEYyour_llm_api_key_here
configZAI_BASE_URLNo novita.ai LLM API base URL
configLLM_MODELgpt-3.5-turbo
configMULTI_EXCHANGE_ENABLED
configDEFAULT_EXCHANGE
configAVAILABLE_EXCHANGES
configLLM_ROUTER_MODELgpt-3.5-turbo
configLLM_TEMPERATURENo 0.7 LLM response creativity (0-1)
configLLM_MAX_TOKENSFor faster small-talk replies, consider a lighter LLM_ROUTER_MODEL and smaller (e.g., 512–2048).
🔐 secretBYBIT_API_KEYyour_bybit_api_key
🔐 secretBYBIT_API_SECRETyour_bybit_secret
configBYBIT_TESTNETNo false Use Bybit testnet
configBOT_AUTH_USERNAME
🔐 secretBOT_AUTH_PASSWORD
configBOT_AUTH_STORE
configMCP_ENABLED
configAPI_DOCS_PATH
configDEFAULT_CATEGORY
configMAX_API_RETRIES
configBYBIT_PUBLIC_ONLY4. Set =false to enable private endpoints
configBOT_AUTH_REQUIREDNo false Require authentication for bot
configBYBIT_ENVIRONMENT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — natural_trading_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tickers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_kline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/vanszs-bybit-autotrade-a3rydt)](https://m8ven.ai/mcp/vanszs-bybit-autotrade-a3rydt)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 738ed3bf0c46365d81493f86f26c60a6b54c68ef
code hash: 4994aaa02fcba0b2a3715e57f0eee479726b8e6eac93b531327cb0bd29ef5ed8
verified: 6/21/2026, 10:13:36 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client