Ajs Bybit MCP Server

ajs-bybit-mcp npm v0.5.0

Published by ajshawit — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
96/100
Last scanned
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • get_closed_tradesingests untrusted input
  • get_ohlcingests untrusted input
  • options_marketingests untrusted input
  • analyze_pairno sensitive capability
  • assess_combo_riskno sensitive capability
  • calculate_position_sizeno sensitive capability
  • cancel_orderno sensitive capability
  • cancel_rfqno sensitive capability
  • check_rfq_eligibilityno sensitive capability
  • close_option_positionno sensitive capability
  • close_positionno sensitive capability
  • create_rfqno sensitive capability
  • estimate_execution_costno sensitive capability
  • execute_quoteno sensitive capability
  • get_account_statusno sensitive capability
  • get_carry_analyticsno sensitive capability
  • get_event_calendarno sensitive capability
  • get_market_datano sensitive capability
  • get_market_regimeno sensitive capability
  • get_option_payoffno sensitive capability
  • get_performance_statsno sensitive capability
  • get_portfolio_riskno sensitive capability
  • get_volatilityno sensitive capability
  • list_open_ordersno sensitive capability
  • list_tradfi_instrumentsno sensitive capability
  • manage_positionno sensitive capability
  • place_option_tradeno sensitive capability
  • place_tradeno sensitive capability
  • rfq_queryno sensitive capability
  • scan_marketno sensitive capability

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.0 latest A 96/100 0 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ajs-bybit-mcp/badge.svg)](https://mcptrustchecker.com/registry/ajs-bybit-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ajs-bybit-mcp"><img src="https://mcptrustchecker.com/registry/ajs-bybit-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ajs-bybit-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ajs-bybit-mcp --online

Use the free API → How scoring works

More in Finance & Commerce