Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Stakechain

by Abstract36version 0.3.0i★ –iComputer or cloud
Registry nameio.github.Abstract36/stakechain

Install

Overview

Description from the maker (original English)

Live Base staking/lending yields (APY, TVL, vaults) as MCP tools; x402 pay-per-request tier

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://stakechain-api.vercel.app/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "stakechain": {
      "command": "npx",
      "args": [
        "-y",
        "stakechain-mcp"
      ],
      "env": {
        "STAKECHAIN_API": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http stakechain https://stakechain-api.vercel.app/mcp

Or run it on your computer

claude mcp add stakechain --env STAKECHAIN_API=your-value -- npx -y stakechain-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "stakechain": {
      "url": "https://stakechain-api.vercel.app/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "stakechain": {
      "command": "npx",
      "args": [
        "-y",
        "stakechain-mcp"
      ],
      "env": {
        "STAKECHAIN_API": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "stakechain": {
      "type": "http",
      "url": "https://stakechain-api.vercel.app/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "stakechain": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "stakechain-mcp"
      ],
      "env": {
        "STAKECHAIN_API": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://stakechain-api.vercel.app/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • STAKECHAIN_API env
    Yields API base URL

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • list_base_yields

    Survey staking and lending opportunities on Base: APY, TVL, project and asset for each. Use this for breadth — browsing the market, answering 'what is available', or filtering a wide set. It covers pools this server cannot deposit into as well as ones it can. Use something else w

  • best_yield

    The single highest-APY pool on Base for one asset, with junk-farm filters applied (minimum TVL, APY ceiling, no impermanent-loss exposure). Use this for a direct 'where is the best rate for X' question when one answer is wanted rather than a list. Use something else when: you wan

  • list_lending_vaults

    The Base lending shelf an agent can act on: Morpho ERC-4626 vaults, Aave V3 reserves, Moonwell markets and this project's own staking pools, each with the contract address to deposit into (`depositTo`), the asset's address and decimals, and a `risk` block (fee, age, concentration

  • market_profile

    Risk profile for one market, for the moment before capital is committed. Use this when a specific market has been chosen and the question is whether to go ahead. It is the one tool that answers 'what else should I know besides the rate'. Use something else when: you are still cho

  • yield_history

    Daily APY and TVL history for one market, with min, median, max and volatility over the window. Use this for one question only: has this rate held, or did it appear yesterday? Call it before acting on any unusually high rate. Use something else when: you want the other risk facto

  • build_deposit

    Turns a chosen market into signed-ready calldata: an ordered list of transactions to deposit into it or leave it, across Morpho vaults, Aave reserves, Moonwell markets and this project's staking pools — three different protocol interfaces behind one call. The approve step is incl

Basic checksi

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 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Abstract36, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 182 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 6 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32568 servers in this category
  • Published to the registry more recently than 82% of the other 32568 servers in this category
  • Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Stakechain safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 7 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today
Install

README from the maker

Open the README

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.

StakeChain Labs

## ⚠️ Retired 2026-11-05 — not maintained

This project is finished. The daily and weekly schedules are off, nothing is

being updated, and no claim below should be read in the present tense.

It was built to sell DeFi rate data to machines over x402. It worked, and it

earned $0.008 a month. Sweeping the entire x402 discovery index — 3,315

sellers — showed total market revenue of $96,010 per 30 days, of which

71.9% is one gift-card checkout endpoint, and 2,736 sellers earn under $1 a

month. There is no price at which selling data on that rail pays.

Read [POSTMORTEM.md](POSTMORTEM.md) for the numbers, the three

conclusions the data overturned, and what is worth taking from the code.

The deployed links below may still respond; they are not being watched.

Live: landing · dashboard · API · contract on BaseScan · Blockscout

STACH is tradeable: Uniswap v4 pool STACH/ETH live on Base (initial price 4,000,000 STACH/ETH) — routable through aggregators (LI.FI verified).

An open staking-yield experiment on Base. Live aggregator of staking and lending rates across Base protocols — readable by humans on a dashboard, consumable by AI agents over MCP, payable by machines over x402.

No seed round. No token presale. Just a running, open-source experiment. Concept and plan: docs/PIVOT-2026.md.

The product

PieceWhat it does
api/Base yields aggregator with junk-farm filters, rate history and market profiles. Aave and Moonwell are read from their own contracts, not a third-party snapshot; x402 machine-payment endpoints
agents/MCP server (5 tools, on npm) + runnable recipes + a resident analyst that pays the public API for its own data
dashboard/React dashboard: Base Yields, Earn (Morpho, Aave, Moonwell), Borrow, Swap, STACH staking, Portfolio
contracts/STACH token + flexible/locked staking — audited & hardened (audit), plus the treasury timelock — 38 tests
website/Landing page (static, GitHub-Pages-ready)

Legacy 2021–2023 material (Laravel site, old static site, branding, original docs) is kept under website-laravel/, website-static/, branding/, docs/.

Monetization: machines pay, on-chain, automatically — LIVE

Human endpoints (/yields, /vaults) are free. Machine endpoints (/v1/*) speak the x402 protocol with enforcement on: HTTP 402 + payment requirements → the client signs an EIP-3009 USDC authorization ($0.001/request) → it settles on-chain through the Coinbase facilitator, with our own EIP-3009 settler as the fallback (no accounts, no API keys either way). Revenue lands at the admin wallet; api/pay-client.js is a reference paying client.

Embeddable badges: live rates as SVG for any README — see docs/BADGES.md. No key, no signup.

API reference: docs/API.md — endpoints, the x402 flow, MCP tools and what each one answers.

Rate history: /history?pool= &days=30 answers the question a live APY cannot — has this rate held, or did it appear yesterday? Daily snapshots are committed to data/history/ in this repo, so the series is verifiable and survives us. Agents get it as the yield_history tool.

Pricing: ~$0.001/request (pure x402; the three data routes differ by a millionth of a dollar so the settled transfer names which one was bought), or subscriptions bought with a single x402 payment — Developer $19/30d, Professional $99/30d (GET /v1/subscribe/ returns a signed X-API-KEY that skips per-request payments). Public stats: /stats reports payment counts and revenue computed from on-chain USDC transfers — verifiable by anyone on BaseScan.

Real yield: collected USDC is distributed to STACH stakers through RevenueDistributor (verified; merkle epochs reproducible from public state via contracts/scripts/revenue-snapshot.js, 180-day sweep-back).

MCP config

The yields aggregator is an MCP server, published on npm as stakechain-mcp. Add it to any MCP-compatible client:

{

"mcpServers": { "stakechain": { "command": "npx", "args": ["-y", "stakechain-mcp"] } } }

Quickstart

# 1. Yields API

cd api && npm install && npm start # :4000

2. Dashboard

cd dashboard && npm install --legacy-peer-deps npm start # :3000, reads the API

3. Give the data to your AI agent (published on npm, no clone needed)

claude mcp add stakechain -- npx -y stakechain-mcp

4. Contracts (test + cheap deploy)

cd contracts && npm install npx hardhat test # 38 tests npm run deploy:baseSepolia # free testnet

STACH token

Deployed at the same address on both networks (verified via Sourcify, exact match):

Initial holder / admin: 0x2Ab5A19aabc599C1a24CC0541ECB757b56976661. The dashboard targets mainnet by default; set REACT_APP_CHAIN=baseSepolia for the testnet.

Fixed supply 42M. At deployment: 3M held by the contract as the staking reward reserve (1M flexible / 2M locked over 360 days), 39M to the admin wallet. The admin wallet now holds none of it: on 2026-10-31 it moved 24.43M (58.16% of supply) into a Dutch auction and a Uniswap v4 pool initializer — see the table below and docs/TOKENOMICS.md. The 2022 contract had two critical bugs (recipient-burning transferFrom, unbacked reward minting) — fixed and regression-tested in 2026: docs/AUDIT-2026-10.md.

The distributor above is deployed and verified, but carries no meaningful revenue yet — /stats reports the real figure, including how much came from our own agent. Revenue first, distribution second: the mechanism exists so it can be checked, not because there is something to distribute.

Supply transparency

Full detail, including lock schedules and the usage-rewards budget: docs/TOKENOMICS.md.

Every STACH is accounted for (snapshot 2026-11-02, verify on-chain):

HolderAddressSTACHShare
Dutch auction — 58.16% of supply was moved here and to the initializer below on 2026-10-31; terms not yet published, nothing sold so far0xBd0c…FecC712.21M29.08%
Uniswap v4 pool initializer for that auction0xf101…600012.21M29.08%
Uniswap v4 STACH/ETH pool liquidity (not locked)0x4985…2b2b8.14M19.39%
Timelocked treasury — locked until 2027-04-28, linear to 2028-10-19, no owner and no recovery path0x6425…D69C6.30M15.00%
Staking reward reserve (3M) + user stakes, held by the token contract0x82c5…71663.03M7.22%
Deployer (deploys contracts, pays usage rewards)0x2974…734F~100k0.24%
Treasury / operations — now empty0x2Ab5…666100%

15% sits in a verified timelock with no owner, no pause and no recovery function, and 7.22% is the staking reward reserve the token contract can only pay to stakers. About 80% of supply has never been in public hands — the auction and its initializer hold 58.16% between them, and the auction's terms are not published yet, so we cannot tell you here when or at what price those tokens reach the market. Concentration flags remain entirely fair; this table exists so the claim can be checked rather than trusted.

Honest part

This is an experiment, not "the future of finance". Everything here is MIT-licensed, the audit is public, the data endpoints filter out obvious degen traps (min TVL, APY ceiling, no-IL default). Nothing in this repository is financial advice.

Ask PopNx