Injectivelabs Core MCP Server

@injectivelabs/mcp-server-core npm v0.1.0

Published by @injectivelabs — 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.

AI agent library for trading perpetual futures on Injective

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/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 − 1 = 99. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 37

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

  • account_balancesno sensitive capability
  • account_positionsno sensitive capability
  • address_normalizeno sensitive capability
  • authz_grantno sensitive capability
  • authz_revokeno sensitive capability
  • bridge_debridge_inbound_quoteno sensitive capability
  • bridge_debridge_inbound_sendno sensitive capability
  • bridge_debridge_quoteno sensitive capability
  • bridge_debridge_sendno sensitive capability
  • bridge_withdraw_to_ethno sensitive capability
Show 27 more tools ↓
  • cctp_attestation_statusno sensitive capability
  • cctp_mintno sensitive capability
  • cctp_supported_chainsno sensitive capability
  • evm_broadcastno sensitive capability
  • frontend_guidanceno sensitive capability
  • frontend_guidance_topicsno sensitive capability
  • market_listno sensitive capability
  • market_priceno sensitive capability
  • rfq_constantsno sensitive capability
  • rfq_market_readinessno sensitive capability
  • subaccount_depositno sensitive capability
  • subaccount_withdrawno sensitive capability
  • token_metadatano sensitive capability
  • trade_closeno sensitive capability
  • trade_close_eip712no sensitive capability
  • trade_limit_closeno sensitive capability
  • trade_limit_openno sensitive capability
  • trade_limit_ordersno sensitive capability
  • trade_limit_statesno sensitive capability
  • trade_openno sensitive capability
  • trade_open_eip712no sensitive capability
  • transfer_sendno sensitive capability
  • usdc_native_infono sensitive capability
  • wallet_generateno sensitive capability
  • wallet_importno sensitive capability
  • wallet_listno sensitive capability
  • wallet_removeno sensitive capability

What this scan could not see

Versions 1

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.1.0 latest A 99/100 0 1.13.0 2026-09-07

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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/injectivelabs-mcp-server-core/badge.svg)](https://mcptrustchecker.com/registry/injectivelabs-mcp-server-core)
HTML
<a href="https://mcptrustchecker.com/registry/injectivelabs-mcp-server-core"><img src="https://mcptrustchecker.com/registry/injectivelabs-mcp-server-core/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/injectivelabs-mcp-server-core/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 @injectivelabs/mcp-server-core --online

Use the free API → How scoring works

More in Finance & Commerce