Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Live Base staking/lending yields (APY, TVL, vaults) as MCP tools; x402 pay-per-request tier
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
STAKECHAIN_APIDu brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://stakechain-api.vercel.app/mcpÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"stakechain": {
"command": "npx",
"args": [
"-y",
"stakechain-mcp"
],
"env": {
"STAKECHAIN_API": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http stakechain https://stakechain-api.vercel.app/mcpclaude mcp add stakechain --env STAKECHAIN_API=your-value -- npx -y stakechain-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"stakechain": {
"url": "https://stakechain-api.vercel.app/mcp"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"stakechain": {
"command": "npx",
"args": [
"-y",
"stakechain-mcp"
],
"env": {
"STAKECHAIN_API": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"stakechain": {
"type": "http",
"url": "https://stakechain-api.vercel.app/mcp"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"stakechain": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"stakechain-mcp"
],
"env": {
"STAKECHAIN_API": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://stakechain-api.vercel.app/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
STAKECHAIN_API envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Abstract36 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.3.0) kam vor 7 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, SSTracker free youth training
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Free youth sports drills, practice plans and age-group answers for parents and coaches.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
## ⚠️ 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.
| Piece | What 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/.
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).
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"] } } }
# 1. Yields API
cd api && npm install && npm start # :4000
cd dashboard && npm install --legacy-peer-deps npm start # :3000, reads the API
claude mcp add stakechain -- npx -y stakechain-mcp
cd contracts && npm install npx hardhat test # 38 tests npm run deploy:baseSepolia # free testnet
Deployed at the same address on both networks (verified via Sourcify, exact match):
0x82c5f9901CD9AEE3177053482b79aEA235507166 · Blockscout0x82c5…7166 — real STACH stays locked on Base (bridge docs)0x82c5f9901CD9AEE3177053482b79aEA235507166Initial 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.
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):
| Holder | Address | STACH | Share |
|---|---|---|---|
| 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 far | 0xBd0c…FecC7 | 12.21M | 29.08% |
| Uniswap v4 pool initializer for that auction | 0xf101…6000 | 12.21M | 29.08% |
| Uniswap v4 STACH/ETH pool liquidity (not locked) | 0x4985…2b2b | 8.14M | 19.39% |
| Timelocked treasury — locked until 2027-04-28, linear to 2028-10-19, no owner and no recovery path | 0x6425…D69C | 6.30M | 15.00% |
| Staking reward reserve (3M) + user stakes, held by the token contract | 0x82c5…7166 | 3.03M | 7.22% |
| Deployer (deploys contracts, pays usage rewards) | 0x2974…734F | ~100k | 0.24% |
| Treasury / operations — now empty | 0x2Ab5…6661 | 0 | 0% |
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.
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.