ton-mcp-server

MCP server for TON-related functionality, exposing TON capabilities as MCP tools to AI agents.

Evaluated Apr 04, 2026 (19d ago)
Homepage ↗ Repo ↗ Infrastructure mcp ton blockchain developer-tools agent-integration
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
46
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
40
Error Messages
0
Auth Simplicity
50
Rate Limits
10

🔒 Security

TLS Enforcement
60
Auth Strength
40
Scope Granularity
35
Dep. Hygiene
45
Secret Handling
50

Security properties (TLS/auth/secret handling) are not verifiable from the provided input. For self-hosted MCP servers, ensure HTTPS/TLS, least-privilege keys (if any), and avoid logging secrets. Blockchain tool endpoints should validate inputs and protect against SSRF/command injection where external calls are performed.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
30
AF Security Reliability

Use Cases

  • Enable AI agents to interact with TON blockchain workflows via standardized MCP tool calls
  • Support building agentic apps that need TON address/wallet or transaction-related operations
  • Abstract TON operations behind an agent-friendly interface for automation

Not For

  • Using as a general-purpose TON RPC proxy without MCP integration
  • Production systems that require strong, clearly documented operational/SLA guarantees
  • Use cases needing audited smart-contract execution logic beyond what the MCP server explicitly supports

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Likely environment-based credentials or node access depending on deployment
OAuth: No Scopes: No

No concrete authentication details were provided in the supplied content; MCP server auth mechanisms cannot be verified from the request data.

Pricing

Free tier: No
Requires CC: No

Pricing details were not provided; assuming open-source/self-hosted or unspecified cost model.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Blockchain operations may be non-idempotent (e.g., sending transactions) unless the server explicitly provides idempotency keys or safe-retry semantics
  • Agents may need to handle chain latency and eventual-finality delays
  • Tool outputs may be large (e.g., transaction traces), requiring truncation/structured summarization by the agent

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ton-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered