Skip to content

Gexno Web3 MCP server

io.github.JanzenChen/gexno-web3JanzenChenstreamable-httpv0.1.3Scanned

Free Ethereum wallet profile & NFT metadata MCP tools (no signup).

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Gexno Web3 MCP server can do

The Gexno Web3 MCP server is published by the GitHub account JanzenChen. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (lookup_wallet and lookup_nft).

The fixed checks matched 2 findings (base64-blob). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • lookup_nftResolve NFT metadata for a contract + tokenId: name, description, image HTTP URL, IPFS gateway link, and raw metadata JSON.Reads text others write1 finding

    Why it is in this group

    • The name "lookup_nft" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "resolve" and "http": it reads web pages, which anyone can write.

    Findings

    • Warn

      The input schema at examples[0].contract contains a 42-character base64 string.

      Matched text

      inputSchema.examples[0].contract: "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up NFT metadata
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • lookup_walletLook up an Ethereum wallet: ETH balance, contract flag, outbound tx count, and simple risk heuristics (ok / new_wallet / contract / eip7702).Reads text others write1 finding

    Why it is in this group

    • The name "lookup_wallet" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The input schema at examples[0].address contains a 42-character base64 string.

      Matched text

      inputSchema.examples[0].address: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up an Ethereum wallet
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:24 UTC, unchanged since Oct 27, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The input schema at examples[0].address contains a 42-character base64 string.

    Matched text

    inputSchema.examples[0].address: "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"

    What this check looks for
  • The input schema at examples[0].contract contains a 42-character base64 string.

    Matched text

    inputSchema.examples[0].contract: "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools2 changed.~2 changedView diff
    • Changed:lookup_nftOnly readsdescriptioninputSchemaannotations
    • Changed:lookup_walletOnly readsdescriptioninputSchemaannotations

Install

Pinned to version 0.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http gexno-web3 https://api.gexno.com/mcp
claude mcp add --transport http gexno-web3 https://api.gexno.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gexno-web3__lookup_wallet",
      "mcp__gexno-web3__lookup_nft"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gexno-web3. Review it before you use it.

Capability tags behind 2 rules
  • mcp__gexno-web3__lookup_wallet untrusted-input
  • mcp__gexno-web3__lookup_nft untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.JanzenChen/gexno-web3/verify?hash=645512e91461fe97182cbab02a767b82a877e855d018985307585a607334aedb" | jq -e '.changed == false'

Pinned hash 645512e91461, from Nov 9, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.JanzenChen/gexno-web3/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.JanzenChen/gexno-web3
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.JanzenChen/gexno-web3.svg)](https://radar.anlyon.com/servers/io.github.JanzenChen/gexno-web3)

Source: MCP Registry · repository. Synced Oct 27, 2026, 03:17 UTC.

Gexno Web3 MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Gexno Web3 MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Gexno Web3 MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Gexno Web3 MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Gexno Web3 MCP server have?

2 tools: 2 read. lookup_wallet and lookup_nft.

Does the Gexno Web3 MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Gexno Web3 MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Gexno Web3 MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.