Is TONNode — TON blockchain access safe to use?

TONNode — TON blockchain access has an HVTrust score of 22.3/100 (Grade D), ranked #957 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for TONNode — TON blockchain access?

TONNode — TON blockchain access scores 22.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 38 GitHub stars and is categorized under MCP Servers.

TONNode — TON blockchain access

tonnode/mcp

TON MCP server for Claude, ChatGPT, Cursor, Codex and any MCP client — liteserver queries over native ADNL: balances, ac

MCP Servers TypeScript Grade D Listed MIT

22.3/100

Rank #957 of 1283

Compare TONNode — TON blockchain access

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-04 · 8d ago

Recent change

Rank +1

Is TONNode — TON blockchain access safe? TONNode — TON blockchain access scores 22.3/100 (Grade D), ranked #957 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 3% of recent commits are signed; last pushed 2026-08-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#489 Unifi MCP Server — 22.3 (D) → #490 Google Health MCP — 22.3 (D) → #492 Code Index MCP — 22.3 (D) → #493 Airflow MCP Server — 22.2 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 56 spots (#891 → #947)

2026-08-08

Newly Listed

First tracked at rank #885

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for TONNode — TON blockchain access View MCP Servers Report missing data

52.3

Activity sub-score · out of 100

#491

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-04

8 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #959

Analysis

HVTrust Dimensions vs MCP Servers

22.3 / 100 · 40.0% confidence

TONNode — TON blockchain access MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

0.2 / 25

4.8 below avg 5.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

17.5 / 20

5.1 above avg 12.4

AdoptionLog-scaled stars · package downloads

3.8 / 20

2.0 below avg 5.8

Activity Inputs

52.3 / 100

StarsRepository reach

9.5 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

18.8 / 25

CommunityFork signal

0.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Is TONNode — TON blockchain access safe?

Public trust evidence for TONNode — TON blockchain access is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does TONNode — TON blockchain access publish package provenance?

No published build provenance is currently detected for TONNode — TON blockchain access. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does TONNode — TON blockchain access have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for TONNode — TON blockchain access. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is TONNode — TON blockchain access actively maintained?

Maintained. Last push was 8 days ago.

What license does TONNode — TON blockchain access use?

TONNode — TON blockchain access ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are TONNode — TON blockchain access's commits signed?

3% of the last 100 commits to TONNode — TON blockchain access are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

TONNode — TON blockchain access appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain TONNode — TON blockchain access?

For maintainers

HVTrust scores TONNode — TON blockchain access from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Rank Moved

Rank dropped 56 spots (#891 → #947)

2026-08-08

Newly Listed

First tracked at rank #885

GitHub → npm: @tonnode/mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/tonnode-ton-blockchain-access.svg)](https://hvtracker.net/agents/tonnode-ton-blockchain-access)
            
HTML:
            <a href="https://hvtracker.net/agents/tonnode-ton-blockchain-access"><img src="https://hvtracker.net/badge/tonnode-ton-blockchain-access.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON