MoltNode by Chord
REMOTE · MOLTNODE.AG · 2 COMPONENTS
Read 31 blockchains over JSON-RPC and swap via Chord: best route, unsigned tx, simulation. No key.
Available components
Last scanned (9 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (rpc_call). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 795 tokens (~113/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 63
First indexed and scored.
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 17 Oct 2026 · Probed https://moltnode.ag/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moltnode.ag | CN=YE2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 587f58b2c695d7ccb2af4276de203d77015 |
| SANs: *.moltnode.ag, moltnode.ag | ||||||
| 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 moltnode.ag. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ag. | present | 8905, 25471 | 8, 8 | Verified |
| moltnode.ag. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'none' |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://moltnode.ag/mcp | Verified | 200 | |
| http (plaintext) | http://moltnode.ag/mcp | HTTPS enforced | 301 | https://moltnode.ag/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 →
chord_find_token Find a token (Chord) ~93
Find a token by symbol, name or address on a chain Chord trades on (base, ethereum, monad, bnb, avalanche, arbitrum, robinhood, arc). Returns addresses, decimals and whether the token is verified; similar tickers are common, so compare addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chord chain key. |
| query | string | yes | Symbol, name or 0x address. |
No output schema declared.
No examples provided.
chord_swap_quote Swap quote and unsigned transaction (Chord) ~215
Best swap route from Chord (getchord.xyz) across the DEXs of the chain, with the UNSIGNED transaction to sign, the ERC-20 approval it needs (as a ready transaction) and a simulation run from the taker wallet. Amounts are integer strings in the token's smallest unit; the zero address is the native coin. Nothing is sent: sign with your own key, then send_raw_transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount of tokenIn in its smallest unit, e.g. '10000000' = 10 USDC. |
| chain | string | yes | Chord chain key. |
| slippageBps | integer | – | Slippage in basis points (default 50). |
| taker | string | – | The wallet that will sign. With it the answer carries tx + approval + a simulation from that wallet. |
| tokenIn | string | yes | Token sold (zero address = native coin). |
| tokenOut | string | yes | Token bought (zero address = native coin). |
No output schema declared.
No examples provided.
get_balance Native balance ~49
The native-coin balance of an address on an EVM chain, in wei and in whole coins.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Account address. |
| chain | string | yes | EVM chain slug. |
No output schema declared.
No examples provided.
get_block_number Latest block number ~35
The latest block number of an EVM chain, as a decimal integer.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | EVM chain slug. |
No output schema declared.
No examples provided.
list_chains List chains ~48
List every chain MoltNode serves (slug, name, chainId, family, native coin, endpoint) and which ones Chord trades on. Call this first for valid chain slugs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rpc_call JSON-RPC call ~116
Call any JSON-RPC 2.0 method on a chain through MoltNode, no API key. EVM chains use eth_* methods; Solana and Sui use their own.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain slug, e.g. 'ethereum', 'base', 'monad', 'solana'. |
| method | string | yes | JSON-RPC method, e.g. 'eth_call', 'eth_getLogs', 'getBalance'. |
| params | array | – | JSON-RPC params array. Defaults to []. |
No output schema declared.
No examples provided.
send_raw_transaction Broadcast a signed transaction ~73
Broadcast a signed transaction (0x-prefixed raw bytes) on an EVM chain through MoltNode. Returns the transaction hash and an explorer link.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | EVM chain slug. |
| signedTransaction | string | yes | The signed transaction, RLP-encoded, 0x-prefixed. |
No output schema declared.
No examples provided.
How do I install the MoltNode by Chord MCP server?
MoltNode by Chord is a hosted endpoint at https://moltnode.ag/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 · moltnode.ag
claude mcp add --transport http tuantqse90-moltnode 'https://moltnode.ag/mcp'
What is the MoltNode by Chord MCP server?
MoltNode by Chord is an MCP server listed in the public MCP registry as io.github.tuantqse90/moltnode. Read 31 blockchains over JSON-RPC and swap via Chord: best route, unsigned tx, simulation. No key. This page covers its hosted endpoint (https://moltnode.ag/mcp).
Is the MoltNode by Chord MCP server safe to use?
MoltNode by Chord scores 64 out of 100 on VerifyMCP. 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 MoltNode by Chord MCP server expose?
MoltNode by Chord exposes 7 tools: list_chains, rpc_call, get_block_number, get_balance, chord_find_token, and 2 more. Their descriptions and schemas cost roughly 629 tokens of context every time the server is loaded.
Does the MoltNode by Chord MCP server require authentication?
No. We connected to MoltNode by Chord without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MoltNode by Chord MCP server still maintained?
MoltNode by Chord is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.