Comprabtc

Name: Comprabtc
Author: csacanam

by csacanamversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.csacanam/comprabtc

Install

Overview

Description from the maker (original English)

Non-custodial Bitcoin DCA for agent treasuries: approve USDT once, stack WBTC on Celo forever.

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: COMPRABTC_WALLET_PRIVATE_KEY

Install

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

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: COMPRABTC_WALLET_PRIVATE_KEY, COMPRABTC_MAX_PER_RUN_USDT

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "comprabtc": {
      "command": "npx",
      "args": [
        "-y",
        "comprabtc-mcp"
      ],
      "env": {
        "COMPRABTC_WALLET_PRIVATE_KEY": "your-value",
        "COMPRABTC_MAX_PER_RUN_USDT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add comprabtc --env COMPRABTC_WALLET_PRIVATE_KEY=your-value --env COMPRABTC_MAX_PER_RUN_USDT=your-value -- npx -y comprabtc-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": {
    "comprabtc": {
      "command": "npx",
      "args": [
        "-y",
        "comprabtc-mcp"
      ],
      "env": {
        "COMPRABTC_WALLET_PRIVATE_KEY": "your-value",
        "COMPRABTC_MAX_PER_RUN_USDT": "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": {
    "comprabtc": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "comprabtc-mcp"
      ],
      "env": {
        "COMPRABTC_WALLET_PRIVATE_KEY": "your-value",
        "COMPRABTC_MAX_PER_RUN_USDT": "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.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

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

Values you fill in

COMPRABTC_WALLET_PRIVATE_KEY secret env
Treasury/agent wallet that owns the plan (holds USDT, signs setup txs, receives WBTC). Required only for create/renew/cancel; reads work without it.
COMPRABTC_MAX_PER_RUN_USDT env
Safety cap per installment in USDT (default 50, pool-depth guard).

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

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

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 csacanam, 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
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32623 servers in this category
Published to the registry more recently than 23% of the other 32623 servers in this category
Basic checks equal to or better than 100% of the other 32623 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 Comprabtc safe?

It passed 1 of 1 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?

You need to fill in: COMPRABTC_WALLET_PRIVATE_KEY

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

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

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 2 days ago

Install

Draugr

by draugr-dev

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

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.

CompraBTC

Non-custodial Bitcoin DCA agent on Celo. Define your plan once — *$X every hour/day in BTC* — and an on-chain agent buys Bitcoin for you, straight into your own wallet. Funds never leave your wallet between purchases.

Live app: https://comprabtc.vercel.app (works in MiniPay and any injected wallet)
Agent API: https://comprabtc-api.vercel.app (GET / service descriptor · GET /api/stats public metrics)
Built for the Celo Agentic Payments & DeFAI Hackathon — leaderboard

Deployed contracts (Celo mainnet, chain 42220)

Contract	Address
DCAExecutor (verified)	`0xd03ffeBBCaaA8aA21053eEB0EeAde39EFC504189`
USDT (token in)	`0x48065fbBE25f71C9282ddf5e1cD6D6A887483D5e`
WBTC — native bridge (token out)	`0x8aC2901Dd8A1F17a1A4768A6bA4C3751e3995B2D`
Uniswap V3 SwapRouter02	`0x5615CDAb10dc425a742d643d949a7F474C01abc4`

Swaps route through the USDT/WBTC 0.3% Uniswap V3 pool. Protocol fee: 1% + $0.005 flat per execution, with on-chain hard caps (≤1%, ≤$0.05 flat) and a revert if the fee would ever eat the installment.

Agent identity: ERC-8004 #9665 on Celo mainnet (8004scan). Every transaction carries ERC-8021 attribution tags.

How it works

flowchart TB

USER["👤 User wallet (MiniPay / MetaMask / Valora)"] FE["Frontend — Next.js PWA (Vercel)"]

subgraph onchain["⛓️ Celo mainnet"] USDT["USDT (ERC-20)"] EXEC["DCAExecutor 0xd03f…4189 non-custodial, on-chain limits"] ROUTER["Uniswap V3 SwapRouter02 USDT/WBTC 0.3% pool"] TREASURY["Treasury"] end

subgraph backend["🤖 Agent backend — Vercel"] KEEPER["Keeper (Vercel Cron, 5 min) scans PlanCreated events, checks due plans"] API["Express API POST /api/execute (x402-gated, permissionless)"] DB[("Supabase plans · executions")] TG["Telegram bot purchase alerts + ops"] end

FACIL["x402 facilitator api.x402.celo.org"]

USER -- "① approve(budget) — once" --> USDT USER -- "② createPlan(amount, interval) — once" --> EXEC FE -.-> USER KEEPER -- "discovers plans (PlanCreated events)" --> EXEC KEEPER -- "③ pays 0.02 USDT via x402 (EIP-3009 signature)" --> API API -- "verify + settle" --> FACIL API -- "④ execute(user, minOut)

ERC-8021 attribution tags" --> EXEC EXEC -- "⑤ transferFrom

(one installment)" --> USDT EXEC -- "fee 1% + $0.005" --> TREASURY EXEC -- "⑥ swap USDT→WBTC" --> ROUTER ROUTER -- "⑦ WBTC straight to the user's wallet" --> USER API -- "records execution" --> DB API -- "🔔 purchase alert" --> TG

The user approves USDT to DCAExecutor (cap = total plan budget) and creates a plan with on-chain limits (amount per run, minimum interval). Cancelling = one click (cancelPlan or approve(0)).
The keeper discovers plans from PlanCreated events, and each cycle pays the execution API with an x402 micropayment before calling execute() — so every purchase is also an agent-to-agent payment.
On-chain limits mean even a compromised keeper can't overcharge: it can never pull more than amountPerRun or execute before minInterval elapses.
Users get Telegram alerts on every purchase (link from Settings in the app).

Repository layout

Directory	What it is
`contracts/`	`DCAExecutor.sol` (Foundry) — 21 tests incl. mainnet fork tests, deploy script
`backend/`	Express API + keeper loop (viem) + x402 middleware + Supabase + Telegram bot
`frontend/`	Next.js PWA (wagmi/viem) — MiniPay auto-connect, plan creation, BTC portfolio
`docs/`	Unit economics, copy review
`PLAN.md`	Full architecture plan and piece-by-piece feasibility verification

Running locally

Frontend (needs NEXT_PUBLIC_EXECUTOR_ADDRESS, NEXT_PUBLIC_API_URL, NEXT_PUBLIC_ATTRIBUTION_CODE, NEXT_PUBLIC_TELEGRAM_BOT in frontend/.env.local):

cd frontend && pnpm install && pnpm dev   # http://localhost:3000

Backend + keeper (Node 22; see backend/src/config.ts for required env vars — executor address, keeper key, Supabase credentials, x402 API key; DB schema in backend/supabase/schema.sql + migrations in the same folder):

cd backend && pnpm install && pnpm dev    # API on :8080, keeper ticks every 60s

Locally the keeper runs as an in-process loop (setInterval). Deployed on Vercel the whole Express app is a single function and the keeper is driven by Vercel Cron hitting GET /api/cron/keeper (guarded by CRON_SECRET, schedule in backend/vercel.json) — serverless instances are frozen and reused, so an interval there would fire duplicated, off-schedule ticks. Anything the keeper needs to remember between ticks (alert cooldowns, digest cadence, last scanned block) lives in agent_keeper_state, not in memory.

Contracts:

cd contracts && forge test                # unit + Celo mainnet fork tests

forge script script/Deploy.s.sol --rpc-url celo --broadcast --verify --interactives 1

For AI agents

An agent with its own funded wallet can set up a Bitcoin savings plan in two transactions — and so can an agent assisting a human (the web app handles the signing):

MCP server (treasury DCA): claude mcp add comprabtc -- npx -y comprabtc-mcp — tools to check status, create/renew/cancel the plan and track the portfolio, signing with the treasury's own wallet. See mcp/README.md.
Agent skill: npx skills add csacanam/comprabtc — covers plan creation (viem), monitoring, budget math, cancelling, and the permissionless x402 execution trigger.
Service descriptor (machine-readable how-to): GET https://comprabtc-api.vercel.app/ · LLM index: comprabtc.vercel.app/llms.txt
Agent identity: ERC-8004 #9665 on Celo — metadata · 8004scan

Transparency

Operator wallets (declared):

Role	Address
Keeper (executes plans)	`0x2F6a8283546d28506B312013F77aA38e60AF99B0`
Treasury / payTo (receives fees)	`0x6Bd5c303b2ed7E264C1Ce9D3592457292a1F1c43`

On-chain volume is real user capital. Each plan starts with a user's own approve; the keeper pulls one installment per run via transferFrom and the purchased WBTC goes straight to the user's wallet, where it stays. No custody, no round-trips — the volume is actual BTC purchases with real economic intent.

x402 is internal metering with an open door. The keeper pays x402 on every run, so each x402 payment maps to one real executed purchase — not standalone dust. /api/execute is permissionless and auto-registers plans from on-chain events, so any external agent or human can invoke it and settle their own x402; it is not a closed loop.

Hackathon tracks

Track 1 — on-chain revenue: protocol fee charged inside execute(), every tx tagged with ERC-8021 attribution.
Track 2 — x402 payments: the keeper pays /api/execute per run via the Celo x402 facilitator. The endpoint is permissionless — any agent can pay to trigger an execution.
Track 4 — Aigora: agent registered on the Aigora marketplace (#395) + feedback PRs at trionlabs/aigora-skills.

License

MIT

Comprabtc

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Draugr

README from the maker

CompraBTC

Deployed contracts (Celo mainnet, chain 42220)

How it works

Repository layout

Running locally

For AI agents

Transparency

Hackathon tracks

License