Skip to main content
Glama

Gexno Web3 MCP

Free, no-signup on-chain lookups for AI agents. Two read-only tools: wallet profile and NFT metadata.

  • Remote: https://api.gexno.com/mcp — Streamable HTTP, nothing to install

  • npm: npx @gexno/web3-mcp — same tools over stdio

  • Registry name: io.github.JanzenChen/gexno-web3

No API key, no signup, no wallet connection. Reads only.

Tool

What it returns

lookup_wallet

ETH balance, contract flag, outbound tx count, simple risk heuristics (ok / new_wallet / contract / eip7702)

lookup_nft

NFT metadata for contract + tokenId: name, description, image HTTP URL, IPFS gateway link, raw JSON (ERC-721 tokenURI and ERC-1155 uri)

Backed by the Gexno Web3 Agent API: https://api.gexno.com/api/web3

Use it (remote, nothing to install)

{
  "mcpServers": {
    "gexno-web3": {
      "url": "https://api.gexno.com/mcp"
    }
  }
}

Works with Claude Desktop, Cursor, and any MCP client that supports remote servers.

Discovery documents:

Related MCP server: Base Intel MCP

Use it (npm, stdio)

npx -y @gexno/web3-mcp

Client config:

{
  "mcpServers": {
    "gexno-web3": {
      "command": "npx",
      "args": ["-y", "@gexno/web3-mcp"]
    }
  }
}

Requires Node.js >= 20. The stdio process calls the same public HTTP API.

Environment variables

Variable

Default

Purpose

GEXNO_API_BASE

https://api.gexno.com

API root, useful for self-hosted instances

GEXNO_TIMEOUT_MS

35000

Per-request timeout; NFT + IPFS resolution can be slow

GEXNO_INTERNAL_TOKEN

—

Only for self-hosted Gexno APIs that require it. Never commit a value.

Programmatic use

import { TOOLS, createApiGet, runTool } from '@gexno/web3-mcp'

const apiGet = createApiGet({ apiBase: 'https://api.gexno.com' })
const wallet = await runTool('lookup_wallet', { address: '0xd8dA...6045' }, apiGet)

Use it (local bundle, MCPB)

Download gexno-web3.mcpb from Releases and open it in Claude Desktop (drag onto the app, or Settings → Extensions).

What the output looks like

{
  "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "balanceEth": "5.7736",
  "isContract": false,
  "txCount": 5969,
  "risk": "eip7702",
  "eip7702": true,
  "delegation": { "address": "0xd1ea…", "verified": true }
}

EIP-7702 delegated EOAs are reported as risk: "eip7702" with isContract: false — they are still EOAs, they just carry a delegation designator. We parse the 0xef0100 prefix and checksum the delegate address, so a delegated wallet is not misreported as a smart contract.

Limits & behaviour

  • Free tier: short-burst rate limit plus a daily cap per IP; no key required.

  • Cached reads: wallet ~60s, NFT metadata ~5min. Repeat lookups are millisecond-scale.

  • No signup, no tracking, no wallet connection. Reads only.

  • Not an AML/risk score. Heuristics are intentionally simple.

  • Errors surface as normal MCP tool errors; the process does not crash.

Development

npm install
npm run smoke    # live wallet lookup against the API
npm start        # run the stdio server directly

Test against a local API instead of production with GEXNO_API_BASE=http://127.0.0.1:3000.

Security posture and residual risks: HARDENING.md

Available Tools

2 tools
lookup_nftA
Read-onlyIdempotent
Inspect

Resolve NFT metadata for a contract + tokenId: name, description, image HTTP URL, IPFS gateway link, and raw metadata JSON. Supports ERC-721 and ERC-1155. Read-only.

Inputs: tokenId (required), contract (required).

lookup_walletA
Read-onlyIdempotent
Inspect

Look up an Ethereum wallet: ETH balance, contract flag, outbound tx count, and simple risk heuristics (ok / new_wallet / contract / eip7702). EIP-7702 delegated EOAs report risk=eip7702. Read-only; not an AML score.

Inputs: address (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly distinct resources: an Ethereum wallet lookup versus an NFT metadata resolver. Their descriptions make the boundary unambiguous, with no overlap in purpose.

    Naming Consistency5/5

    Both names follow the same predictable lookup_noun pattern (lookup_wallet, lookup_nft). The convention is consistent and easy for an agent to infer.

    Tool Count3/5

    Only two tools are provided, which feels thin for a Web3 server even if the scope is deliberately narrow. Each tool is meaningful, but the surface is borderline minimal.

    Completeness2/5

    The surface covers wallet summaries and NFT metadata only, leaving obvious Web3 gaps such as transaction lookup, ERC-20/token balances, ENS resolution, or contract data. Agents would frequently hit dead ends for common blockchain queries.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to fetch live multi-chain portfolio, token info, gas prices, and token prices across Ethereum, Base, Polygon, Arbitrum, and Optimism with a single call. No API key required.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only on-chain intelligence for AI agents on Base, providing tools to read balances, token metadata, gas, and transaction status live from chain without API keys.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query on-chain data across EVM chains like Base, Optimism, Avalanche, Celo, and Arbitrum, including balances, transactions, gas, and smart contract interactions.
      49 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform pay-per-call security verification of wallets, tokens, contracts, dApps, agents, and more via a remote endpoint with no installation.
      2
      MIT