Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LogicNodes

REMOTE · LOGICNODES.IO

Verified EVM, Aptos and finance tools for AI agents; gas for 14 chains. Pay per call (x402).

Available components

60 Trust /100

Last scanned (5 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6071 tokens (~144/item across 42 items; 42 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 42 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 42 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 22 Oct 26 60

    First indexed and scored.

Diagnostics

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 22 Oct 2026 · Probed https://logicnodes.io/mcp/v2

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=logicnodes.io CN=YE2,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA384 62eec9c738e82f6b97da2fea158ed134ddc
SANs: *.logicnodes.io, logicnodes.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 logicnodes.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 8 Verified
logicnodes.io. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://logicnodes.io/mcp/v2 Verified 200
http (plaintext) http://logicnodes.io/mcp/v2 HTTPS enforced 301 https://logicnodes.io/mcp/v2
MCP tools · 42 exposed · ~6,071 tokens

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 →

Tool Tokens
address_format_check ~108

Checks whether a string is a well-formed address for EVM (EIP-55 checksum), Solana, Aptos (AIP-40) or Bitcoin (base58check, bech32, bech32m). With family "auto" it lists every family the string could be, and never picks one. A valid format is not evidence an address is safe, owned, or the one you meant.

NameTypeReqDescription
addressstringyes–
familystringyes–

No output schema declared.

No examples provided.

address_validate ~124

Validates an address for a chain and returns its canonical form. EVM: EIP-55 (a wrong checksum is refused, never corrected). Aptos: AIP-40 strict form. Says only what can be known offline; it never guesses what kind of account an address is.

NameTypeReqDescription
addressstringyes–
chainstring|numberyesCAIP-2 chain id such as eip155:8453 (Base) or aptos:1; a bare EVM chain id number also works. Chain names like "base" are refused.

No output schema declared.

No examples provided.

aptos_address_validate ~175

Validates an address against the Aptos address standard (AIP-40) and returns its canonical form: special addresses (0x0-0xf) as short form, all others as 0x + 64 digits. Strict by default; mode=relaxed also accepts a missing 0x or a few dropped leading zeros, and says which spelling you used (a truncated-looking address is always refused). With lookup=true it checks the chain to say whether the address is an account, an object, or neither, at one ledger version.

NameTypeReqDescription
addressstringyes–
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
lookupboolean––
modestring––

No output schema declared.

No examples provided.

aptos_amount_convert ~118

Converts between a human decimal amount and integer base units, using the asset's decimals read LIVE from the chain (never assumed from a symbol). Refuses to round: more decimal places than the asset has is an error. An ambiguous symbol returns AMBIGUOUS_INPUT.

NameTypeReqDescription
amountstringyes–
assetstringyes–
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
directionstringyes–

No output schema declared.

No examples provided.

aptos_asset_resolve ~161

[PAID $0.001 USDC per call via x402] Turns a symbol, registry id, fungible-asset address or coin type into one asset, with its on-chain symbol/name/decimals read live. Several different assets share the symbols USDC and USDT (Circle/Tether native vs LayerZero-bridged); those return AMBIGUOUS_INPUT with every candidate, its issuer and how to select it. Assets outside the registry are returned with verified:false, never silently trusted.

NameTypeReqDescription
caseSensitiveboolean––
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
querystringyes–

No output schema declared.

No examples provided.

aptos_balance_get ~190

[PAID $0.002 USDC per call via x402] Balances of an address for APT and fungible assets, all read at ONE ledger version (stated, or the current one pinned). Amounts are exact integer strings plus decimal strings. Default assets: APT and every verified asset; pass `assets` (symbols, ids, addresses, coin types) to choose. An ambiguous symbol fails the whole call. An address with no account and all-zero balances is reported honestly, not as an empty account.

NameTypeReqDescription
addressstringyes–
assetsarray––
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
ledgerVersion––read the chain exactly as of this ledger version (default: the current one, pinned for consistency)

No output schema declared.

No examples provided.

aptos_fee_estimate ~152

[PAID $0.005 USDC per call via x402] Gas unit price tiers (deprioritized/regular/prioritized) plus the cost of common transactions in octas, APT and USD. Gas units are MEASURED by simulating real transfers now, not taken from a table. USD comes only from two independent exchanges that agree; otherwise USD is explicitly unavailable. Transaction types: apt_transfer, apt_transfer_new_account; for anything else use aptos_tx_simulate.

NameTypeReqDescription
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
txTypesarray––

No output schema declared.

No examples provided.

aptos_name_resolve ~150

[PAID $0.001 USDC per call via x402] name -> address, or address -> primary name (give exactly one). A name resolves to its TARGET address, which can differ from its owner; a registered name with no target resolves to nothing (NOT_FOUND) and its owner is never substituted. An address's primary name is returned only if that name resolves forward to the same address, so a spoofed reverse record is never trusted.

NameTypeReqDescription
addressstring––
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
namestring––

No output schema declared.

No examples provided.

aptos_tx_decode ~149

[PAID $0.002 USDC per call via x402] Explains what an entry-function payload would do, in plain English, with every argument type-checked against the module ABI and amounts shown using the asset's live decimals. Known patterns (transfers, batch transfers, key rotation, code publishing) carry a risk flag from a fixed table; no flag means 'not recognised', never 'safe'.

NameTypeReqDescription
argumentsarray––
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
functionstringyes–
typeArgumentsarray––

No output schema declared.

No examples provided.

aptos_tx_simulate ~212

[PAID $0.005 USDC per call via x402] Runs an UNSIGNED entry-function transaction through the node's own simulator (no key needed, nothing is submitted) and returns success or the abort decoded in plain English, exact gas and fee, balance changes, and events. Arguments are type-checked against the module ABI first. Balance changes count only the framework's Withdraw/Deposit events, so assets that re-emit them (like USDC) are never double-counted. A simulation runs against the node's current state and cannot be pinned to an older ledger version.

NameTypeReqDescription
argumentsarray––
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
functionstringyes–
gasUnitPrice–––
maxGasAmount–––
senderstringyes–
sequenceNumber–––
typeArgumentsarray––

No output schema declared.

No examples provided.

aptos_tx_status ~120

[PAID $0.001 USDC per call via x402] Committed, failed, pending or not found for a transaction hash, with the VM status explained in plain English (Move aborts decoded to module, error name, code and category; the raw status is always included). Fee is computed from the VM's own fee statement.

NameTypeReqDescription
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
hashstringyes–

No output schema declared.

No examples provided.

aptos_view ~196

[PAID $0.002 USDC per call via x402] Calls a Move #[view] function read-only, after checking every type argument and argument against the module's ABI: u64/u128/u256 must be decimal strings, vector<u8> a 0x hex string, Option<T> written {"vec":[]} or {"vec":[value]}, addresses in AIP-40 form. A wrong argument is a specific error from us, never an opaque node error. Optionally reads at a stated ledger version.

NameTypeReqDescription
argumentsarray––
chainstring–Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)
functionstringyes–
ledgerVersion––read the chain exactly as of this ledger version (default: the current one, pinned for consistency)
typeArgumentsarray––

No output schema declared.

No examples provided.

business_days ~120

[PAID $0.001 USDC per call via x402] Counts business days between two dates, adds business days to a date, or tests whether a date is a business day. Weekends are configurable. NO holidays are assumed: pass the holidays you want observed. Dates are calendar dates (YYYY-MM-DD) with no time zone.

NameTypeReqDescription
daysinteger––
fromstringyes–
holidaysarray––
opstringyes–
tostring––
weekendstring––

No output schema declared.

No examples provided.

chain_info ~97

Describes a supported chain: CAIP-2 id, display name, native currency, block explorers, and exactly which operations it supports. Omit `chain` to list every supported chain.

NameTypeReqDescription
chainstring|number–CAIP-2 chain id such as eip155:8453 (Base) or aptos:1; a bare EVM chain id number also works. Chain names like "base" are refused.

No output schema declared.

No examples provided.

decimal_calc ~133

Add, subtract, multiply, divide, raise to an integer power, compare, or take a percentage, on decimal STRINGS with exact arithmetic (no floating point). The result is rounded only to the scale and rule you choose, and the response says whether rounding changed the value. JSON numbers are refused because they lose precision. Division by zero is an error.

NameTypeReqDescription
astringyes–
bstringyes–
opstringyes–
roundingstring–rounding rule; default half_up (ties away from zero). half_even is banker's rounding
scaleinteger––

No output schema declared.

No examples provided.

erc8004_agent ~96

Reads an agent from the ERC-8004 identity registry on Base: its owner address and the registration URI it points to, at one stated block. The URI is reported, not fetched (fetching arbitrary URLs for you is not this tool's job). An id that was never minted is NOT_FOUND.

NameTypeReqDescription
agentIdstringyesERC-8004 agent id (decimal string)
blockstring––

No output schema declared.

No examples provided.

erc8004_reputation ~133

Summarises the feedback posted about an agent in the ERC-8004 reputation registry on Base, at one block: number of distinct clients, number of feedback entries, the registry's own summary value, and each client's latest entry (value, tags, revoked). It is EVIDENCE, not a verdict: anyone can post feedback from any address, so many clients is not proof of many people, and tag text is free text written by the client (shown as untrusted).

NameTypeReqDescription
agentIdstringyesERC-8004 agent id (decimal string)
blockstring––

No output schema declared.

No examples provided.

evm_allowance ~208

[PAID $0.002 USDC per call via x402] How much a spender may take from an owner for a token, at one block, in exact base units and human units, flagging 'unlimited' approvals.

NameTypeReqDescription
blockstring–"latest" (default), "safe", "finalized", or a decimal block number. Every value in the answer is read at this one block
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.
ownerstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
spenderstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
tokenstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)

No output schema declared.

No examples provided.

evm_balance ~213

[PAID $0.002 USDC per call via x402] Native and ERC-20 balances of an address, ALL read at one stated block (number and hash returned). Token decimals are read from the token contract, never assumed; an address with no code, or a contract that is not a standard ERC-20, is an error and is never reported as a zero balance. Amounts are exact strings.

NameTypeReqDescription
addressstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
assetsarray–"native" and/or token contract addresses; default ["native"]
blockstring–"latest" (default), "safe", "finalized", or a decimal block number. Every value in the answer is read at this one block
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.

No output schema declared.

No examples provided.

evm_block ~138

[PAID $0.001 USDC per call via x402] Number, hash, timestamp, base fee (gwei), gas used/limit and transaction count of one block. Use block "finalized" for a block that can no longer reorganize.

NameTypeReqDescription
blockstring–"latest" (default), "safe", "finalized", or a decimal block number. Every value in the answer is read at this one block
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.

No output schema declared.

No examples provided.

evm_calldata_decode ~124

[PAID $0.001 USDC per call via x402] Decodes transaction calldata against an ABI that YOU supply and returns the function, its signature and each argument. If the selector is not in your ABI it says so and lists the selectors it does have; it does not guess from a selector database. An ABI that does not belong to the target contract can decode to plausible nonsense.

NameTypeReqDescription
abiarrayyesJSON ABI objects, or human-readable signatures such as "function transfer(address to, uint256 amount)"
datastringyes–

No output schema declared.

No examples provided.

evm_contract_type ~192

[PAID $0.003 USDC per call via x402] Says what is at an address using on-chain evidence: empty account, EIP-7702 delegated account, EIP-1167 minimal proxy, EIP-1967 proxy (with implementation and admin), Safe wallet (with owners and threshold), or other contract. Each classification lists the evidence. It is not a safety verdict.

NameTypeReqDescription
addressstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
blockstring–"latest" (default), "safe", "finalized", or a decimal block number. Every value in the answer is read at this one block
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.

No output schema declared.

No examples provided.

evm_log_decode ~112

[PAID $0.001 USDC per call via x402] Decodes one event log (its topics and data) against an ABI that YOU supply and returns the event name and arguments. If no event in your ABI matches topic0 it says so rather than guessing from a database of known events.

NameTypeReqDescription
abiarrayyesJSON ABI objects, or human-readable signatures such as "function transfer(address to, uint256 amount)"
datastringyes–
topicsarrayyes–

No output schema declared.

No examples provided.

evm_logs ~156

[PAID $0.003 USDC per call via x402] Logs emitted by one contract in a block range of at most 2000 blocks, optionally filtered by topics. Refuses (rather than truncates) when more than 1000 logs match, so an answer is always complete.

NameTypeReqDescription
addressstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.
fromBlockstringyes–
toBlockstringyes–
topicsarray––

No output schema declared.

No examples provided.

evm_nonce ~149

[PAID $0.001 USDC per call via x402] The transaction count of an address at one stated block. Pending-pool transactions are not counted, and the answer says so.

NameTypeReqDescription
addressstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
blockstring–"latest" (default), "safe", "finalized", or a decimal block number. Every value in the answer is read at this one block
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.

No output schema declared.

No examples provided.

evm_spend_report ~155

[PAID $0.005 USDC per call via x402] Every transfer of one ERC-20 token out of (or into) a wallet across a block range of up to 20,000 blocks, with exact amounts, per-counterparty totals, per-UTC-day totals, and an accounting CSV. Reads public chain data only. The range is queried in full 2000-block pieces and the report refuses (rather than truncates) when more than 2000 transfers match.

NameTypeReqDescription
chainstringyes–
directionstring––
fromBlockstringyes–
toBlockstringyes–
tokenstringyes–
walletstringyes–

No output schema declared.

No examples provided.

evm_token_metadata ~172

[PAID $0.002 USDC per call via x402] Name, symbol, decimals and total supply of an ERC-20 read from its contract at one block. Handles tokens whose name/symbol are bytes32. If decimals() is missing, it is an error: decimals are never assumed.

NameTypeReqDescription
blockstring–"latest" (default), "safe", "finalized", or a decimal block number. Every value in the answer is read at this one block
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.
tokenstringyes0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)

No output schema declared.

No examples provided.

evm_tx_receipt ~114

[PAID $0.002 USDC per call via x402] Status (success / reverted / pending), block, gas used and the exact fee in wei and native units for a transaction hash. 'Not found' is reported as such and is not proof the transaction never existed.

NameTypeReqDescription
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.
hashstringyes–

No output schema declared.

No examples provided.

gas_estimate ~165

[PAID $0.001 USDC per call via x402] Current fee tiers for a chain as decimal strings with explicit units. EVM: confidence levels (default 99/95/90/80/70) in gwei with base fee, priority fee and max fee. Aptos: deprioritized/regular/prioritized gas unit prices in octas per gas unit. Data older than its freshness budget is an error, never a stale answer.

NameTypeReqDescription
chainstring|numberyesCAIP-2 chain id such as eip155:8453 (Base) or aptos:1; a bare EVM chain id number also works. Chain names like "base" are refused.
confidenceLevelsarray–EVM only

No output schema declared.

No examples provided.

get_gas_prices ~163

Current gas price estimates for an EVM chain in Blocknative-compatible format (gwei). Default chain is Ethereum (1). Supported chain IDs: 1, 8453, 42161, 10, 137, 56, 43114, 59144, 534352, 324, 100, 81457, 5000, 42220.

NameTypeReqDescription
chainIdinteger–EVM chain ID, e.g. 1 (Ethereum), 8453 (Base). Default 1.
chainidinteger–Alias of chainId (the REST spelling).
confidenceLevelsarray–Confidence levels to return. Default 99, 95, 90, 80, 70.

No output schema declared.

No examples provided.

interest_calc ~143

[PAID $0.001 USDC per call via x402] Exact simple or compound interest for a principal, an annual percentage rate and a term in years, compounded annually, semiannually, quarterly, monthly, weekly or daily. The number of periods must be whole; fractional periods are refused, not approximated. Also returns the effective annual rate.

NameTypeReqDescription
compoundingstringyes–
principalstringyes–
ratePercentstringyes–
roundingstring–rounding rule; default half_up (ties away from zero). half_even is banker's rounding
scaleinteger––
yearsstringyes–

No output schema declared.

No examples provided.

list_supported_chains ~22

EVM chains with live gas data, with chain IDs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

loan_calc ~123

[PAID $0.001 USDC per call via x402] Monthly payment, total interest and total paid for a fixed-rate amortizing loan, in exact arithmetic. The payment is rounded once to the currency scale and the final payment absorbs the rounding so the balance ends at exactly zero.

NameTypeReqDescription
annualRatePercentstringyes–
principalstringyes–
roundingstring–rounding rule; default half_up (ties away from zero). half_even is banker's rounding
scaleinteger––
termMonthsintegeryes–

No output schema declared.

No examples provided.

money_calc ~181

[PAID $0.001 USDC per call via x402] Rounds, adds, subtracts, multiplies, or splits an amount of an ISO 4217 currency, using that currency's real number of minor units (JPY 0, USD 2, KWD 3). A currency not in the list is refused, never assumed to have 2 decimals. split divides a total into equal parts or by ratios so the parts always add back to the total exactly.

NameTypeReqDescription
amountstringyes–
currencystringyes–
factorstring––
opstringyes–
otherstring––
partsinteger––
ratiosarray––
roundingstring–rounding rule; default half_up (ties away from zero). half_even is banker's rounding

No output schema declared.

No examples provided.

payment_verify ~222

[PAID $0.002 USDC per call via x402] Given a transaction hash, lists the ERC-20 transfers in its receipt and, if you give expectations (payee, asset, amount, payer), says whether a successful transaction contains a matching transfer. Use it to check an x402 or other USDC payment. A match proves tokens moved; it does not prove what the payment was for.

NameTypeReqDescription
amountstring–base units
assetstring–0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.
hashstringyes–
payTostring–0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)
payerstring–0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)

No output schema declared.

No examples provided.

random_from_block ~137

[PAID $0.002 USDC per call via x402] Deterministic, publicly recomputable random integers derived from a FINALIZED block hash and a salt. Refuses a block that is not yet final. Not secret and not for cases where the salt can be chosen after seeing the block.

NameTypeReqDescription
blockstringyes–
chainstringyesEVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused.
countintegeryes–
maxintegeryes–
saltstringyes–

No output schema declared.

No examples provided.

slippage_bounds ~104

[PAID $0.001 USDC per call via x402] From a quoted amount in base units (integer string) and a slippage tolerance in basis points, computes the minimum you should accept (min_out, rounded down) or the maximum you should pay (max_in, rounded up). Integer arithmetic only; the rounding direction is stated.

NameTypeReqDescription
amountstringyes–
directionstringyes–
slippageBpsintegeryes–

No output schema declared.

No examples provided.

swap_price_impact ~125

[PAID $0.001 USDC per call via x402] For a Uniswap-V2-style pool, computes the exact output of a swap (the router's integer formula), the total cost versus the spot price including the fee, and the part due to trade size alone, in basis points. Inputs are reserves and amounts in base units. Does not know any pool: you supply the reserves.

NameTypeReqDescription
amountInstringyes–
feeBpsinteger––
reserveInstringyes–
reserveOutstringyes–

No output schema declared.

No examples provided.

time_convert ~91

Converts an ISO 8601 instant, or a local time plus its IANA zone, to another IANA zone. A local time skipped by a daylight-saving jump is refused; one that occurs twice returns AMBIGUOUS_INPUT with both instants. Zone abbreviations such as EST are refused.

NameTypeReqDescription
fromZonestring––
timestringyes–
toZonestringyes–

No output schema declared.

No examples provided.

token_amount_convert ~183

Converts between a human decimal amount and integer base units without ever rounding: too many decimals is an error. Decimals are never assumed: pass `decimals`, or an `asset` whose decimals are read from the chain (EVM: "native" or an ERC-20 token address, whose decimals() is read live from the chain; Aptos: any asset, with live decimals; an ambiguous symbol such as USDC returns AMBIGUOUS_INPUT with every option).

NameTypeReqDescription
amountstringyes–
assetstring––
chainstring|numberyesCAIP-2 chain id such as eip155:8453 (Base) or aptos:1; a bare EVM chain id number also works. Chain names like "base" are refused.
decimalsinteger––
directionstringyes–

No output schema declared.

No examples provided.

tx_status ~116

[PAID $0.001 USDC per call via x402] Whether a transaction is committed, failed, pending or not found, with a plain-English explanation. 'Not found' is reported as such and is not proof the transaction never existed.

NameTypeReqDescription
chainstring|numberyesCAIP-2 chain id such as eip155:8453 (Base) or aptos:1; a bare EVM chain id number also works. Chain names like "base" are refused.
hashstringyes–

No output schema declared.

No examples provided.

unit_convert ~129

Converts length, mass, volume, time, data, energy, area, speed and temperature using exact definitions (an inch is exactly 0.0254 m). Ambiguous names (oz, gal, pt, KB) return AMBIGUOUS_INPUT with the choices instead of picking one. Reports whether the result is exact or rounded.

NameTypeReqDescription
fromstringyes–
roundingstring–rounding rule; default half_up (ties away from zero). half_even is banker's rounding
scaleinteger––
tostringyes–
valuestringyes–

No output schema declared.

No examples provided.

Install

How do I install the LogicNodes MCP server?

LogicNodes is a hosted endpoint at https://logicnodes.io/mcp/v2, 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 · logicnodes.io

# add to Claude Code
claude mcp add --transport http io-logicnodes-tools 'https://logicnodes.io/mcp/v2'
Common questions

What is the LogicNodes MCP server?

LogicNodes is an MCP server listed in the public MCP registry as io.logicnodes/tools. Verified EVM, Aptos and finance tools for AI agents; gas for 14 chains. Pay per call (x402). This page covers its hosted endpoint (https://logicnodes.io/mcp/v2).

Is the LogicNodes MCP server safe to use?

LogicNodes scores 60 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 LogicNodes MCP server expose?

LogicNodes exposes 42 tools: get_gas_prices, list_supported_chains, chain_info, gas_estimate, address_validate, and 37 more. Their descriptions and schemas cost roughly 6,071 tokens of context every time the server is loaded.

Does the LogicNodes MCP server require authentication?

No. We connected to LogicNodes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LogicNodes MCP server still maintained?

LogicNodes is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.