# Gexno Web3 (remote · api.gexno.com)

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

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-27

## Components

- remote · `api.gexno.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/janzenchen-gexno-web3/api.md), [page](https://verifymcp.io/servers/janzenchen-gexno-web3/api)

## Channel facts

- Endpoint: `https://api.gexno.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-27.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 94/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 372 tokens (~186/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Tools include usage examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Gexno Web3 MCP server?

Gexno Web3 is a hosted endpoint at https://api.gexno.com/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.

### Claude

```bash
claude mcp add --transport http janzenchen-gexno-web3 'https://api.gexno.com/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "janzenchen-gexno-web3": {
      "type": "http",
      "url": "https://api.gexno.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.janzenchen-gexno-web3]
url = "https://api.gexno.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "janzenchen-gexno-web3": {
      "type": "remote",
      "url": "https://api.gexno.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add janzenchen-gexno-web3 --url 'https://api.gexno.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  janzenchen-gexno-web3:
    url: "https://api.gexno.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "janzenchen-gexno-web3": {
      "Transport": "http",
      "Url": "https://api.gexno.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add janzenchen-gexno-web3 -t streamable-http -u 'https://api.gexno.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "janzenchen-gexno-web3": {
      "type": "http",
      "url": "https://api.gexno.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-27 (score 79, +16)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → partial
- [security improvement] HSTS header: fail → pass
- [security] Tool “lookup_nft” rewrote its description, which is the text the model reads
- [security] Tool “lookup_wallet” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Schema quality: fail → pass
- [functional] Server version: 0.1.2 → 0.1.3

### 2026-10-26 (score 63)

First indexed and scored.

## MCP tools (2)

### `lookup_wallet` (~185 tokens)

Look up an Ethereum wallet on-chain profile: ETH balance, whether the address is a smart contract, outbound transaction count, and simple risk heuristics (ok / new_wallet / contract / eip7702). Use when the user asks to check a wallet, query address balance, or get a quick chain risk snapshot. Not an AML score. EIP-7702 delegated EOAs are reported as risk=eip7702 (not as contracts). Read-only lookup with no side effects. Example: lookup_wallet {"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"} returns {"balanceEth":"5.77...","txCount":5969,"risk":"eip7702"}.

Input parameters:

- `address` (string, required): Ethereum address (0x-prefixed, 40 hex chars)

### `lookup_nft` (~187 tokens)

Resolve NFT metadata for a contract + tokenId: name, description, image HTTP URL, IPFS gateway link, and raw metadata JSON. Supports ERC-721 tokenURI and ERC-1155 uri. Use when the user asks for NFT metadata, token image, or to parse IPFS NFT JSON. tokenId must be a decimal string (or integer). Read-only lookup with no side effects. Example: lookup_nft {"contract":"0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D","tokenId":"1"} returns the Bored Ape #1 metadata with an erc721 standard marker and imageHttp URL.

Input parameters:

- `contract` (string, required): NFT contract address (0x-prefixed, 40 hex chars)
- `tokenId` (required): Token ID as decimal string or non-negative integer

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/janzenchen-gexno-web3/api#diagnostics

## Score history

- 2026-10-27: 79
- 2026-10-26: 63

## Common questions

### What is the Gexno Web3 MCP server?

Gexno Web3 is an MCP server listed in the public MCP registry as io.github.JanzenChen/gexno-web3. Free Ethereum wallet profile & NFT metadata MCP tools (no signup). This page covers its hosted endpoint (https://api.gexno.com/mcp).

### Is the Gexno Web3 MCP server safe to use?

Gexno Web3 scores 79 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 Gexno Web3 MCP server expose?

Gexno Web3 exposes 2 tools: lookup_wallet, lookup_nft. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.

### Does the Gexno Web3 MCP server require authentication?

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

### Is the Gexno Web3 MCP server still maintained?

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

## Links

- Remote endpoint: https://api.gexno.com/mcp
- Repository: https://github.com/JanzenChen/gexno-web3
- Changelog RSS feed: https://verifymcp.io/servers/janzenchen-gexno-web3/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/janzenchen-gexno-web3/api.json
- HTML version of this page: https://verifymcp.io/servers/janzenchen-gexno-web3/api