Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mrvlyouknowwho/ton-jetton-risk-mcp

MCPB · TON-JETTON-RISK-MCP-0.2.0.MCPB · SCANNED SEP 20

Token rug/honeypot risk screening: EVM (7 chains, live sell simulation), Solana, TON. Free, keyless.

0 this week 61 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security23
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 417 tokens (~139/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

mcpb · ton-jetton-risk-mcp-0.2.0.mcpb

Download bundle
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed mcpb/https://github.com/mrvlyouknowwho/ton-jetton-risk-mcp/releases/download/v0.2.0/ton-jetton-risk-mcp-0.2.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~417 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
assess_evm_token_risk ~172

Rug-pull / honeypot risk screen for an ERC-20 token on Ethereum, BSC, Base, Arbitrum, Polygon, Optimism or Avalanche. Returns a 0-100 risk score plus flags: honeypot (static analysis + live buy/sell simulation on ETH/BSC/Base), buy/sell tax, owner powers (mint, pause, blacklist, balance change), hidden owner, proxy, open-source status, DEX liquidity and holder concentration. Sources: GoPlus token_security + honeypot.is simulation, live on-chain data. Free.

NameTypeReqDescription
addressstringyesToken contract address (0x-prefixed).
chainstringyesChain: ethereum | bsc | base | arbitrum | polygon | optimism | avalanche (or numeric chain id).

No output schema declared.

No examples provided.

assess_solana_token_risk ~125

Rug-pull risk screen for an SPL token on Solana by mint address. Returns a 0-100 risk score plus flags: active mint/freeze authority, balance-mutable authority, closable accounts, non-transferable, transfer hooks/fees, DEX liquidity (TVL, top pools) and holder concentration. Note: tokens minted minutes ago may return sparse data (dataSparse=true) — treat those as unverified, not safe. Source: GoPlus Solana. Free.

NameTypeReqDescription
addressstringyesSPL token mint address (base58).

No output schema declared.

No examples provided.

assess_ton_jetton_risk ~120

Rug-pull / honeypot risk screen for a TON jetton (token) by its master address. Returns a 0-100 risk score plus flags: mint authority not revoked, admin present, holder concentration, few holders, no DEX liquidity, taxable transfer, DEX blacklist, and a honeypot heuristic. Sources: live on-chain reads (TonAPI) + STON.fi. Free.

NameTypeReqDescription
addressstringyesTON jetton master address, friendly form preferred (EQ... / UQ...).

No output schema declared.

No examples provided.

Common questions

What is the io.github.mrvlyouknowwho/ton-jetton-risk-mcp server?

io.github.mrvlyouknowwho/ton-jetton-risk-mcp is listed in the public MCP registry as io.github.mrvlyouknowwho/ton-jetton-risk-mcp. Token rug/honeypot risk screening: EVM (7 chains, live sell simulation), Solana, TON. Free, keyless. This page covers its MCPB bundle (https://github.com/mrvlyouknowwho/ton-jetton-risk-mcp/releases/download/v0.2.0/ton-jetton-risk-mcp-0.2.0.mcpb).

Is the io.github.mrvlyouknowwho/ton-jetton-risk-mcp server safe to use?

io.github.mrvlyouknowwho/ton-jetton-risk-mcp scores 61 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.mrvlyouknowwho/ton-jetton-risk-mcp server expose?

io.github.mrvlyouknowwho/ton-jetton-risk-mcp exposes 3 tools: assess_evm_token_risk, assess_solana_token_risk, assess_ton_jetton_risk. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.

What licence is the io.github.mrvlyouknowwho/ton-jetton-risk-mcp server under?

io.github.mrvlyouknowwho/ton-jetton-risk-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.