Tld MCP Server

mcp-server-tld npm v1.10.2

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 JustLend V1 DAO on TRON blockchain. Supports supply, borrow, repay, withdraw, market data, mining rewards (USDD/WBTC), API integration, general TRON chain utilities, and AI-guided DeFi prompts.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/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 − 5 = 95. 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
−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 37

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

  • get_token_balancereads sensitive data
  • approve_jst_for_votingno sensitive capability
  • approve_underlyingno sensitive capability
  • borrowno sensitive capability
  • cast_voteno sensitive capability
  • check_allowanceno sensitive capability
  • check_jst_allowance_for_votingno sensitive capability
  • claim_rewardsno sensitive capability
  • deposit_jst_for_votesno sensitive capability
  • enter_marketno sensitive capability
Show 27 more tools ↓
  • estimate_lending_energyno sensitive capability
  • exit_marketno sensitive capability
  • get_account_data_from_apino sensitive capability
  • get_account_summaryno sensitive capability
  • get_all_marketsno sensitive capability
  • get_dashboard_from_apino sensitive capability
  • get_jtoken_details_from_apino sensitive capability
  • get_locked_votesno sensitive capability
  • get_market_datano sensitive capability
  • get_markets_from_apino sensitive capability
  • get_mining_rewardsno sensitive capability
  • get_proposal_listno sensitive capability
  • get_protocol_summaryno sensitive capability
  • get_supported_marketsno sensitive capability
  • get_supported_networksno sensitive capability
  • get_trx_balanceno sensitive capability
  • get_usdd_mining_configno sensitive capability
  • get_user_vote_statusno sensitive capability
  • get_vote_infono sensitive capability
  • get_wallet_addressno sensitive capability
  • get_wbtc_mining_configno sensitive capability
  • repayno sensitive capability
  • supplyno sensitive capability
  • withdrawno sensitive capability
  • withdraw_allno sensitive capability
  • withdraw_votes_from_proposalno sensitive capability
  • withdraw_votes_to_jstno 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.10.2 latest A 95/100 0 1.13.0 2026-09-09

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

Use the free API → How scoring works

More in Developer Tools