TONNode — TON blockchain access
REMOTE · MCP.TONNODE.IO · 2 COMPONENTS · SCANNED OCT 4
TON liteservers over ADNL: balances, history, get-methods, non-custodial DEX and cross-chain swaps
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
No category breakdown is available for this channel yet.
How do I install the TONNode — TON blockchain access MCP server?
TONNode — TON blockchain access is a hosted endpoint at https://mcp.tonnode.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.tonnode.io
claude mcp add --transport http tonnode-mcp 'https://mcp.tonnode.io/mcp'
{
"mcpServers": {
"tonnode-mcp": {
"url": "https://mcp.tonnode.io/mcp"
}
}
} {
"servers": {
"tonnode-mcp": {
"type": "http",
"url": "https://mcp.tonnode.io/mcp"
}
}
} [mcp_servers.tonnode-mcp] url = "https://mcp.tonnode.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tonnode-mcp": {
"type": "remote",
"url": "https://mcp.tonnode.io/mcp",
"enabled": true
}
}
} openclaw mcp add tonnode-mcp --url 'https://mcp.tonnode.io/mcp' --transport streamable-http
mcp_servers:
tonnode-mcp:
url: "https://mcp.tonnode.io/mcp" {
"McpServers": {
"tonnode-mcp": {
"Transport": "http",
"Url": "https://mcp.tonnode.io/mcp"
}
}
} assistant mcp add tonnode-mcp -t streamable-http -u 'https://mcp.tonnode.io/mcp'
{
"mcpServers": {
"tonnode-mcp": {
"type": "http",
"url": "https://mcp.tonnode.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
We have not recorded any changes for this component yet
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 9 Oct 2026 · Probed https://mcp.tonnode.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.tonnode.io | CN=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5306c520891e29898091f4a2d68f9104cc8 |
| SANs: mcp.tonnode.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.tonnode.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tonnode.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="TONNode MCP", error_description="Send your API key as: Authorization: Bearer <key>. Get one at https://tonnode.io/dashboard"
Bearer realm="TONNode MCP", error_description="Send your API key as: Authorization: Bearer <key>. Get one at https://tonnode.io/dashboard"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| www-authenticate | Bearer realm="TONNode MCP", error_description="Send your API key as: Authorization: Bearer <key>. Get one at https://tonnode.io/dashboard" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tonnode.io/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.tonnode.io/mcp | HTTPS enforced | 308 | https://mcp.tonnode.io/mcp |
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 →
No tool schema has been captured from this endpoint yet.