Sonic Blockchain MCP Server (Tairon-ai/sonic-mcp) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 17 tools. No publisher has claimed this listing.

D
Caution
58/100

Sonic Blockchain MCP Server

Enables interaction with the Sonic blockchain including wallet management, token transfers, staking, and bridging between Ethereum and Sonic networks.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

Tairon-ai

Source: Glama

Operator pattern detected
This publisher (tairon-ai) operates 13 MCPs in our catalog. Median trust score: 56.
Computed 2026-09-17
  • · median trust 56 ≤ 60
  • · 92% of MCPs are D or F
  • · wallet-grade env vars shared across MCPs: WALLET_PRIVATE_KEY (×8)
  • · 3 risk keywords appear in ≥2 of the operator's MCPs (top: "private key" ×7, "mnemonic" ×6, "seed phrase" ×2)

Operator-pattern signals come from machine analysis of every MCP under this publisher's GitHub org. They are factual aggregates — not accusations. Investigate the individual MCPs before drawing conclusions.

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

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
⚠️
Known vulnerabilities in dependencies: 15 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
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 1 credential: WALLET_PRIVATE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

generate_wallet

Generate a new Sonic blockchain wallet with address, private key, and mnemonic phrase

check_balance

Check wallet balances. For Sonic: native S token and common ERC20 tokens (wS, WETH, USDC). For Ethereum: native ETH only. If address is not provided, uses WALLET_ADDRESS from environment.

get_token_price

Get the current price of the native S token in USD

get_network_staking_stats

Get network-wide staking statistics including current APR, total stake, and daily rewards

get_staking_validators

Get list of all available validators for staking. Returns validator IDs and names to help users choose which validator to stake to.

transfer

Transfer native S token or ERC20 tokens to another address. Supports token symbols (S, wS, WETH, USDC) or token contract addresses. If private key is not provided, uses WALLET_PRIVATE_KEY from environment.

stake

Stake S tokens to a validator on Sonic blockchain. If private key is not provided, uses WALLET_PRIVATE_KEY from environment.

unstake

Unstake S tokens from a validator on Sonic blockchain. If private key is not provided, uses WALLET_PRIVATE_KEY from environment.

get_staking_info

Get staking information for a wallet address and validator. If address is not provided, uses WALLET_ADDRESS from environment.

claim_rewards

Claim staking rewards from a validator. If private key is not provided, uses WALLET_PRIVATE_KEY from environment.

bridge_to_sonic

STEP 1: Deposit tokens from Ethereum to Sonic bridge. Supports: ETH (auto-wrapped to WETH), USDC, USDT, or custom ERC20 address. Returns depositId and blockNumber - save these!

check_bridge_status

STEP 2: Check if bridge deposit is ready to claim on Sonic. Use blockNumber from bridge_to_sonic response.

claim_on_sonic

STEP 3: Claim bridged tokens on Sonic after deposit is ready. Use depositId, token (symbol or address), amount, and blockNumber from bridge_to_sonic response. Token decimals are automatically detected.

bridge_to_ethereum

STEP 1: Withdraw tokens from Sonic to Ethereum bridge. ⚠️ ONLY supports: WETH, USDC, USDT (by symbol or address). Native S and wS tokens CANNOT be bridged. Returns withdrawalId and blockNumber - save these!

check_withdrawal_status

STEP 2: Check if withdrawal is ready to claim on Ethereum. Use blockNumber from bridge_to_ethereum response.

claim_on_ethereum

STEP 3: Claim withdrawn tokens on Ethereum after withdrawal is ready. Use withdrawalId, token (symbol or address), and amount from bridge_to_ethereum response. Token decimals are automatically detected.

get_token_info

Get information about an ERC20 token (name, symbol, decimals) by its contract address

// known CVEs in dependencies15 high4 medium11 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.7.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.7.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.6.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.6.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configETHEREUM_EXPLORER_URL
configETHEREUM_RPC_URL"": "https://eth-mainnet.g.alchemy.com/v2/YOUR_API_KEY"
configETH_STATE_ORACLE
configETH_TOKEN_DEPOSIT
configETH_TOKEN_PAIRS
configPRICE_API_URL
configSONIC_BRIDGE
configSONIC_EXPLORER_API
configSONIC_EXPLORER_URL
configSONIC_MESSAGE_BUS
configSONIC_MULTICALL3
configSONIC_RPC_URL"": "https://rpc.soniclabs.com",
configSONIC_RPC_URL_BACKUP
configSONIC_SFC
configSONIC_STATE_ORACLE
configSONIC_TOKEN_PAIRS
configSONIC_UPDATE_MANAGER
configSONIC_USDC
configSONIC_WETH
configSONIC_WRAPPED_S
configWALLET_ADDRESS"": "your_wallet_address_here",
🔐 secretWALLET_PRIVATE_KEY"": "your_private_key_here",
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

17/17 tools missing one or more hints — generate_wallet (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_balance (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_token_price (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.7.0 (high), @modelcontextprotocol/sdk@1.7.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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/tairon-ai/sonic-mcp?variant=verified)](https://m8ven.ai/mcp/tairon-ai/sonic-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 93fdc7f7ba3e72e5157ce1f80f627cf93bc612e6
code hash: fedc89ca45dc37212515c5deb162c09f69853a8e2d5800f3705fa0687c315d81
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