LensExtract x402 On-Chain Data

● Active

io.github.alkeke45-cpu/lens-x402-onchain-mcp

Web extraction and live on-chain/crypto data tools, paid per call in Base USDC via x402.

Category
Crypto & Web3
Version
0.1.0
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 21, 2026

Looks healthy: LensExtract x402 On-Chain Data is maintained, open source.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as io.github.alkeke45-cpu/lens-x402-onchain-mcp in the official MCP registry, version 0.1.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
1 required
Declared environment variables: LENS_X402_PRIVATE_KEY. They stay on your machine; the config on this page shows where each goes.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

JavaScript

From the README

LensExtract x402 On-Chain MCP An open-source MCP (Model Context Protocol) server that connects MCP clients — Claude Desktop, Cursor, VS Code, Hermes Agent — to the LensExtract x402 API (https://lens-extract-x402.alkeke45.workers.dev): web-page extraction plus live on-chain / crypto-market data, paid per call in USDC on Base with the x402 protocol. No API keys, no subscriptions — each tool call settles its own micropayment. Listed in the Official MCP Registry as io.github.alkeke45-cpu/lens-x402-onchain-mcp. Tools All Base prices are USDC on Base (chain 8453), paid to the API operator 0x8488E45d428a3B2BC7116c8657b8FF23Cd042ef6. How payment works The API answers unpaid calls with HTTP 402 and an x402 v2 PAYMENT-REQUIRED challenge. This server wraps fetch with the official @x402/fetch client and the @x402/evm exact scheme: it signs an EIP-3009 USDC transferWithAuthorization with your wallet key and retries with a PAYMENT-SIGNATURE header. The API's facilitator settles on Base. Your key is used locally only — it is never sent anywhere. You need a Base wallet holding a small amount of USDC (a dollar covers hundreds of calls). Without a key, the free discovery tool still works and paid tools return the API's payment requirements instead of data. Install MCPB bundle (Claude Desktop) Download lens-x402-onchain-mcp.mcpb from the latest GitHub release and open it with Claude Desktop (or double-click it).…

Read the full README on GitHub →

The most-starred Crypto & Web3 servers in the index, with their live-check result.

ServerStarsLast pushLive check
Oh My Posh Validator23,772Nov 2026Working
Solana MCP by Vybe2,728Oct 2026Working
Solana MCP by Vybe2,728Oct 2026Working
Oracle3 prediction-market agent tools569Nov 2026Local / not checked
Flyto Core483Nov 2026Local / not checked

LensExtract x402 On-Chain Data: questions people ask

Is LensExtract x402 On-Chain Data a remote or a local MCP server?
According to its entry in the official MCP registry, LensExtract x402 On-Chain Data ships as a local package (mcpb) that your client starts on your machine.
Does LensExtract x402 On-Chain Data need an API key?
Its registry entry declares one required environment variable: LENS_X402_PRIVATE_KEY. The config on this page shows where each goes.
Is LensExtract x402 On-Chain Data safe to use?
Looks healthy: LensExtract x402 On-Chain Data is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: 1 required. Serverdex check of Nov 21, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is LensExtract x402 On-Chain Data still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
How do I add LensExtract x402 On-Chain Data to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Crypto & Web3 →

Add the badge to your site

Show visitors that LensExtract x402 On-Chain Data is listed here — it’s also the link we check for a free listing.

LensExtract x402 On-Chain Data — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-alkeke45-cpu-lens-x402-onchain-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="LensExtract x402 On-Chain Data — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![LensExtract x402 On-Chain Data — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-alkeke45-cpu-lens-x402-onchain-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).