Arbitrum MCP Server

arbitrum-mcp npm v1.0.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for interfacing with the Arbitrum system (nodes, chains, accounts, ecosystem) in natural language

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 38

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

  • arb_check_publisher_healthno sensitive capability
  • arb_get_raw_block_metadatano sensitive capability
  • arb_latest_validatedno sensitive capability
  • arbdebug_validateMessageNumberno sensitive capability
  • arbdebug_validationInputsAtno sensitive capability
  • arbos_versionno sensitive capability
  • arbtrace_blockno sensitive capability
  • arbtrace_callno sensitive capability
  • arbtrace_callManyno sensitive capability
  • arbtrace_filterno sensitive capability
Show 28 more tools ↓
  • arbtrace_getno sensitive capability
  • arbtrace_replayBlockTransactionsno sensitive capability
  • arbtrace_replayTransactionno sensitive capability
  • arbtrace_transactionno sensitive capability
  • assertion_statusno sensitive capability
  • auctioneer_submitAuctionResolutionTransactionno sensitive capability
  • batch_posting_statusno sensitive capability
  • chain_infono sensitive capability
  • clear_rpc_urlno sensitive capability
  • comprehensive_chain_statusno sensitive capability
  • gas_statusno sensitive capability
  • get_balanceno sensitive capability
  • get_balance_etherno sensitive capability
  • get_rollup_addressno sensitive capability
  • get_rpc_urlno sensitive capability
  • get_transactionno sensitive capability
  • get_transaction_receiptno sensitive capability
  • is_contractno sensitive capability
  • latest_blockno sensitive capability
  • list_chainsno sensitive capability
  • maintenance_statusno sensitive capability
  • maintenance_triggerno sensitive capability
  • node_healthno sensitive capability
  • node_peersno sensitive capability
  • search_chainsno sensitive capability
  • set_rpc_urlno sensitive capability
  • sync_statusno sensitive capability
  • timeboost_sendExpressLaneTransactionno 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
v1.0.1 latest A 98/100 0 1.13.0 2026-09-08

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

Use the free API → How scoring works

More in Finance & Commerce