Home / MCP registry index / io.logicnodes/tools

LogicNodes

io.logicnodes/tools in the official MCP registry. Endpoint https://logicnodes.io/mcp/v2.

The registry describes it as: Verified EVM, Aptos and finance tools for AI agents; gas for 14 chains. Pay per call (x402).

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http tools https://logicnodes.io/mcp/v2

{
  "mcpServers": {
    "tools": {
      "url": "https://logicnodes.io/mcp/v2"
    }
  }
}

code --add-mcp '{"name":"tools","type":"http","url":"https://logicnodes.io/mcp/v2"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_gas_prices list_supported_chains x402_service_search chain_info address_validate token_amount_convert evm_balance tx_status token_price x402_settlement_verify tx_safety_check counterparty_check sanctions_check gas_estimate aptos_address_validate aptos_name_resolve aptos_asset_resolve aptos_amount_convert aptos_balance_get aptos_fee_estimate aptos_tx_simulate aptos_tx_decode aptos_tx_status aptos_view decimal_calc slippage_bounds swap_price_impact money_calc interest_calc loan_calc unit_convert address_format_check time_convert business_days evm_nonce evm_block evm_tx_receipt evm_token_metadata evm_allowance evm_contract_type evm_logs evm_calldata_decode evm_log_decode payment_verify random_from_block erc8004_agent erc8004_reputation evm_spend_report ens_resolve wallet_watch_create wallet_watch_status wallet_watch_cancel audit_log_create audit_log_append audit_log_export deal_dispute_review operator_verify_start operator_verify_check agent_register_prepare agent_register_publish and 5 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-logicnodes-tools/badge.svg)](https://lazaretto.dev/mcp-registry/io-logicnodes-tools)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers · Finance and markets MCP servers