Crypto Options Desk MCP (dasein108/crypto_options_desk_mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
69/100
2 months ago

Crypto Options Desk MCP

An MCP server that gives an LLM agent a typed, audited tool surface over quant crypto-options desk analytics: gamma exposure, vanna, skew, vol surface, options flow, technicals, portfolio greeks, scenario analysis, and live positions.

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

dasein108

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 2 credentials: BYBIT_API_KEY, BYBIT_API_SECRET
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_KEYclaude mcp add trading-mcp --env =xxx --env BYBIT_API_SECRET=yyy -- trading-mcp
🔐 secretBYBIT_API_SECRETclaude mcp add trading-mcp --env BYBIT_API_KEY=xxx --env =yyy -- trading-mcp
configMCP_LOG_FILE/tmp/mcp-trading.log Where the server logs (never stdout — stdio is the JSON-RPC channel)
configCC_ASSET
configCC_PAPER_MODE
configCC_IV_RV_THRESHOLD
configCC_TARGET_DELTA
configCC_QTY
configCC_POLL_INTERVAL
configCC_LOG_DIR
// 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

22/22 tools missing one or more hints — get_gex_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_vanna_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_flow_analysis (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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 inputs are validated

21/22 tool handlers declare input schemas (95%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 5/22 tool handlers wrap calls in try/catch (23%)

Wrap each tool handler body in try/catch and return a structured error response.

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 5 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/dasein108-crypto-options-desk-mcp-23n4hi)](https://m8ven.ai/mcp/dasein108-crypto-options-desk-mcp-23n4hi)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b6f9d5c0bd94be37a22e49d5b840297c3cf00107
code hash: 14863b60a5e5ab2c946f3bd23efc613dfe16bc019deee10f23589ef0309bf954
verified: 6/18/2026, 11:07:19 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