bybit-ws (poliakarmai/bybit-ws) is an MCP server listed on the M8ven Trust Index. It scores 41 out of 100, grade D. It declares 14 tools. No publisher has claimed this listing.

Warning

41/100

bybit-ws

Item: bybit-ws
Rating: 41
Author: M8ven

An MCP server that enables AI agents to scan the market, manage positions, and retrieve trading metrics for Bybit through natural language commands.

→ poliakarmai/bybit-ws · listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

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

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

poliakarmai

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

🚨

Secret credentials may flow to a network call

8 flows detected: CRYPTOBOT_TOKEN. We can’t prove the destination matches the brand the credential belongs to.

🚨

Reads files from sensitive locations

Touches: ~/.hermes/.env, ~/.hermes/.env

🔐

You'll be asked for 11 credentials: BYBIT_API_KEY, BYBIT_API_SECRET, BYBIT_HMAC_SECRET, OPENAI_API_KEY, BINANCE_API_KEY, BINANCE_API_SECRET, OKX_API_KEY, OKX_API_SECRET, CRYPTOBOT_TOKEN, GRIDSIGNAL_BOT_TOKEN, EMERGENCY_TOKEN

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.

🔐 secretBYBIT_API_KEY

🔐 secretBYBIT_API_SECRET

configBYBIT_WS_BB_ENABLED

configBYBIT_ML_ENABLED

configBYBIT_WORLD_MODEL

configBYBIT_OPTUNA_ENABLED

configBYBIT_ATR_TP_ENABLED

configBYBIT_DSPY_ENABLED

🔐 secretBYBIT_HMAC_SECRET

configBYBIT_WS_PRODUCTION

🔐 secretOPENAI_API_KEY

configOPENAI_BASE_URL

configBYBIT_ENTRY_JUDGE_ENABLED

configBYBIT_EXCHANGE

🔐 secretBINANCE_API_KEY

🔐 secretBINANCE_API_SECRET

🔐 secretOKX_API_KEY

🔐 secretOKX_API_SECRET

configOKX_PASSPHRASE

🔐 secretCRYPTOBOT_TOKEN

configGRIDSIGNAL_ADMIN_ID

configGRIDSIGNAL_ADMIN_NOTIFY_CHAT

🔐 secretGRIDSIGNAL_BOT_TOKEN

configBYBIT_REGIME_AUTO

configBYBIT_WS_FULL_ENABLED

configNTFY_SERVER

configNTFY_TOPIC

configPUSH_ENABLED

🔐 secretEMERGENCY_TOKEN

configBYBIT_DATA_DIR

configBYBIT_AB_ENABLED

configBYBIT_PAPER_ENABLED

// 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

14/14 tools missing one or more hints — scan_market (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_positions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_metrics (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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.

Tool test coverage

Only 1/14 tools referenced in tests (7%)

Write tests that reference each tool by name so every tool has at least one test.

No access to sensitive paths

Reads sensitive paths: ~/.hermes/.env, ~/.hermes/.env

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 4 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 Verified](https://m8ven.ai/badge/mcp/poliakarmai/bybit-ws?variant=verified)](https://m8ven.ai/mcp/poliakarmai/bybit-ws)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 428ebcab80ed7e418fc1416797565e323a450644

code hash: 20de8c208d6be562aa1f6d7e85caeff0a2f9946659de9c1e5d9af395b0fec179

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