DexSQL
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Query an EVM contract's indexed history with SQL, via a local nuthatch nest and nuthatch dev.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 23/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install nuthatch. Follow https://mcp.popnx.com/i/nuthatch-org-nuthatch.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
SettingsDeveloperEdit Config
{
"mcpServers": {
"nuthatch": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/nuthatch-org/nuthatch:5.22.0",
"mcp",
"--url",
"http://host.docker.internal:8288"
]
}
}
}Use nuthatch and tell me what you can do for me, then show me one thing✓ If Claude says it is using nuthatch or shows a nuthatch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect nuthatch yet
nuthatch runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect nuthatch
B · Others in Crypto & blockchain that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Docker on your computer first (one time)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user nuthatch -- docker run -i --rm ghcr.io/nuthatch-org/nuthatch:5.22.0 mcp --url http://host.docker.internal:8288You should see nuthatch listed as connected
Use nuthatch and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using nuthatch or shows a nuthatch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Docker on your computer first (one time)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Use nuthatch and tell me what you can do for me, then show me one thing✓ If Cursor says it is using nuthatch or shows a nuthatch tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Docker on your computer first (one time)
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Use nuthatch and tell me what you can do for me, then show me one thing✓ If VS Code says it is using nuthatch or shows a nuthatch tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user nuthatch -- docker run -i --rm ghcr.io/nuthatch-org/nuthatch:5.22.0 mcp --url http://host.docker.internal:8288Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"nuthatch": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/nuthatch-org/nuthatch:5.22.0",
"mcp",
"--url",
"http://host.docker.internal:8288"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nuthatch": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/nuthatch-org/nuthatch:5.22.0",
"mcp",
"--url",
"http://host.docker.internal:8288"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"nuthatch": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/nuthatch-org/nuthatch:5.22.0",
"mcp",
"--url",
"http://host.docker.internal:8288"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
oci: ghcr.io/nuthatch-org/nuthatch:5.22.0Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account nuthatch-org, which owns the repo
Code last changed yesterday
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/nuthatch-org-nuthatch)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (5.22.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.
Blockchain data across 100+ chains: token prices, NFTs, transfers, simulation, traces, Solana DAS
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.
| This one nuthatch | DexSQL | PayRam | DexPaprika | Alchemy MCP Server | X402 List MCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 2/3 | 3/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | NOASSERTION | – | MIT | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Turn an EVM contract's history into a local SQL database. One Rust binary, no Postgres, no
subgraph to write, and an MCP server built in.
· Website: www.nuthatch-indexer.com
For AI coding agents: AGENTS.md is install, init, a headless dev, query and MCP setup for every common client, as commands to paste.
Also: self-hosted Etherscan-compatible history for the chains that lost their free tier. Base and BNB Chain, plus Gnosis, on your own RPC (Base and BNB Chain need an archive node with tracing): examples/paywalled-chains.
curl -fsSL https://nuthatch-indexer.com/install.sh | sh
export PATH="$HOME/.local/bin:$PATH" mkdir weth-nest && cd weth-nest nuthatch init 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 --alias weth nuthatch dev --backfill 300
Then, in a second terminal:
nuthatch sql "SELECT count(*) FROM weth__transfer"
The installer covers macOS Apple Silicon and Linux x86_64 and aarch64, and the export adds its directory, which a fresh macOS shell lacks. init indexes WETH and detects its chain. The block carries no # comments because zsh, the macOS default, does not treat a pasted # as one: it passes the rest of the line on as arguments.
The Linux binary needs glibc 2.35 or newer to run from 4.1.0, which is also what it is built on; 4.0.x ran on 2.34; older systems and Alpine have a static x86_64 build. On other platforms, build from source with Rust 1.95.0 (docs/install.md).
mkdir weth-nest is where the nest goes. init writes nuthatch.toml, abis/ and the rest into the current directory, and an empty one keeps a home directory clear of them. init creates a nest: the directory, holding the contract's ABI, its config and, once dev runs, its indexed data. --backfill 300 starts 300 blocks behind the tip, about an hour of mainnet, so there are rows to query within seconds on the bundled public endpoints. Without it, dev backfills from the contract's deployment block: for WETH that is 21 million blocks, a long backfill on free public endpoints and a job for your own RPC (--rpc).
That quickstart, run as written on the 4.10.1 release on 2026-10-05, took 13 s from the curl to a non-zero count in a clean macOS shell on an M5 Pro, and 21 s in a fresh ubuntu:24.04 container (docs/readme-check-2026-10-05.md, which records every command in this file). The mkdir line is newer than that timing.
The endpoints a new nest is given are for this try-out. On the bundled mainnet pair, nuthatch doctor reports eth_getLogs windows of 160 blocks (Tenderly) and 80 (mevblocker), and both are rate-limited. A 300-block window of USDC went over Tenderly's 20,000-log cap, so the same --backfill 300 that finishes for WETH can stall on a busier contract.
Use your own node or a paid endpoint. --rpc replaces the bundled pool. The first command below keeps the recent window. The second backfills from the deployment block:
nuthatch dev --backfill 300 --rpc https://your-endpoint.example
nuthatch dev --rpc https://your-endpoint.example
The same URL can live in nuthatch.toml as rpc_urls instead of --rpc. More, including how to probe an endpoint first, is under Bring your own RPC endpoint.
| Needs a subgraph | Needs handler code | Data comes from | What you run | Query with | |
|---|---|---|---|---|---|
| The Graph | yes | yes (AssemblyScript) | indexers on the network | nothing, or graph-node + Postgres + IPFS | GraphQL |
| Ponder | no | yes (TypeScript) | your RPC endpoint | Node.js, plus Postgres in production | SQL, GraphQL |
| nuthatch | no | no: tables come from the ABI | your RPC endpoint | one binary | SQL, HTTP, MCP |
Like Ponder, nuthatch reads the chain over JSON-RPC, so it needs an endpoint, and a provider may charge for one. The public endpoints it bundles are for trying it out, not for keeping it running. It complements The Graph rather than replacing it: a subgraph serves an application from a network of indexers, while a nest puts a contract's history in a database on your own machine.
Why. Getting at a contract's history usually means writing a subgraph or handler code, running a database, or renting someone else's copy. nuthatch generates the tables from the ABI, runs as one process with nothing else to install, and keeps the data on your machine: at most 2 GB of RAM per chain, no telemetry unless you opt in, no account. The built-in MCP server lets Claude or any MCP client query it.
init 0xAddr resolves the ABI (Sourcify, then Etherscan), generates the schema and decoders, and scaffolds the project. You write nothing.init (nuthatch count), and its totals are public. Most people say no or are never asked, so they are floors.An earlier example, now finished: [Arcaidia](https://arcaidia.io), a speed layer over Circle's CCTP built at ETHOnline 2026, read its indexed state from two nests on Ethereum Sepolia and Arc Testnet: its solver discovered intents there, its settlement agent tracked CCTP there, and its web console rendered from them. The nests were stopped on 2026-09-29.
More at nuthatch-indexer.com/stories.
There is no hosted platform. We will run a nest for you on the stock binary, with no billing and no accounts: ask on the Discord.
curl -fsSL https://nuthatch-indexer.com/install.sh | sh
That downloads the prebuilt binary for your platform from the latest release, verifies its SHA-256, and installs it to ~/.local/bin (override with NUTHATCH_INSTALL_DIR). No compiler is involved. A stock macOS shell does not have ~/.local/bin on its PATH, which is why the quickstart above exports it; add the same line to ~/.zshrc (or ~/.bashrc) to keep it for new terminals. Prebuilt binaries cover macOS on Apple Silicon and Intel and Linux x86_64 and aarch64 (aarch64 from the release after 4.11.0, Intel Mac from the release after 5.16.0) and are attached to every release with their checksums, if you would rather fetch one by hand. The Intel Mac binary is the default build only and has not yet been run on Intel hardware.
The Linux binary is dynamically linked and needs one thing, measured off the published artifact with objdump -T rather than inferred:
GLIBC_2.34, so 2.34 was what you needed to run it and 2.35 only what we compiled it on (#978); 4.1.0 references hypot at GLIBC_2.35, where libm re-versioned it, so the two numbers now agree.It links libc, libm and libgcc and no C++ runtime. Releases before 4.1 embedded DuckDB and also needed libstdc++ from GCC 11.
Debian 12 and Ubuntu 22.04 clear it. RHEL 9 and Amazon Linux 2023 ship glibc 2.34 and ran 4.0.x; from 4.1.0 they need the source build, or nuthatch-x86_64-unknown-linux-musl.tar.gz, a static build with no glibc floor (from the release after 5.16.0; it uses musl's allocator, not jemalloc, so its behaviour under load is unmeasured).
Verify who built it. Every release binary carries a build provenance attestation, which a checksum cannot give you:
gh attestation verify nuthatch-x86_64-unknown-linux-gnu.tar.gz --repo nuthatch-org/nuthatch \
--signer-workflow nuthatch-org/nuthatch/.github/workflows/release.yml --source-ref refs/tags/v
From source, which is the only route on a platform we do not publish a binary for:
rustup toolchain install 1.95.0
cargo +1.95.0 install --git https://github.com/nuthatch-org/nuthatch nuthatch
The +1.95.0 is required: cargo install --git ignores the repo's toolchain pin, and a newer default toolchain fails to compile a dependency.
Container images are published per release to ghcr.io/nuthatch-org/nuthatch - : for embedded, : -scaled for the scaled build. The image ships the *same binary attached to the release*, so the two cannot drift.
docs/install.md has the detail behind each of these: how the ABI floor is measured, what the attestation proves and what --repo is for, and why the toolchain pin exists.
Chains. Ethereum, Arbitrum One, Base, BSC, Polygon, Gnosis, Optimism, Monad and Robinhood Chain are *built in*, with measured public endpoints and tuned finality settings - omit `--chain` and nuthatch probes each for your contract's bytecode and picks the one it lives on. Point at your own node with --rpc.
Any other EVM chain works too - World Chain, Base Sepolia, your own devnet. Name the chain and say where it lives:
nuthatch init 0xADDR --chain world-chain --rpc https://your-endpoint.example
The chain id is read from the endpoint itself, so there is nothing to look up or type wrong. On one of the nine built-in names --rpc is not consulted for the chain id, but it is the pool: your endpoints replace the bundled public ones outright. Omit --rpc on an unregistered name and the refusal tells you the remedy.
See running an unlisted EVM chain for the finality caveat, which is the part worth reading: a chain whose finalized tag runs close to the tip needs a depth-based policy instead, or you seal immutable Parquet that could never be corrected.
nuthatch assumes a paid RPC endpoint, or your own node, for anything you intend to keep running. That is the golden path.
Worth knowing, since we are being precise about it: most figures currently in docs/benchmarks.md were measured against *public* endpoints, and that is a known weakness of those numbers rather than a recommendation - a benchmark taken through a rate-limited endpoint measures the endpoint. On one workload the network was 99.3% of backfill wall clock (the same tape live against a public endpoint and replayed from disk, 2026-08-23, in docs/benchmarks.md), which is why the replay rig (RFC-0039) exists and why those figures carry that caveat on the page itself.
The free public endpoints bundled per chain exist for one job: so init → dev works with zero setup. Treat them as testing and initial validation. Why they are not fine for rea