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

Billium

by BilliumHQversion 0.1.3i★ –iRuns on your computer
Registry nameio.github.BilliumHQ/billium

Install

Overview

Description from the maker (original English)

Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.

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.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Crypto & blockchain
  • You need to fill in: BILLIUM_API_KEY, BILLIUM_MERCHANT_ID

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: BILLIUM_API_KEY, BILLIUM_MERCHANT_ID, BILLIUM_BASE_URL

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?

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": {
    "billium": {
      "command": "npx",
      "args": [
        "-y",
        "@billium/mcp"
      ],
      "env": {
        "BILLIUM_API_KEY": "your-value",
        "BILLIUM_MERCHANT_ID": "your-value",
        "BILLIUM_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add billium --env BILLIUM_API_KEY=your-value --env BILLIUM_MERCHANT_ID=your-value --env BILLIUM_BASE_URL=your-value -- npx -y @billium/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": {
    "billium": {
      "command": "npx",
      "args": [
        "-y",
        "@billium/mcp"
      ],
      "env": {
        "BILLIUM_API_KEY": "your-value",
        "BILLIUM_MERCHANT_ID": "your-value",
        "BILLIUM_BASE_URL": "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": {
    "billium": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@billium/mcp"
      ],
      "env": {
        "BILLIUM_API_KEY": "your-value",
        "BILLIUM_MERCHANT_ID": "your-value",
        "BILLIUM_BASE_URL": "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

  • BILLIUM_API_KEY secret required env
    Secret API key (sk_...), from the dashboard under Settings → Developer → API keys.
  • BILLIUM_MERCHANT_ID required env
    Merchant ID (mer_...).
  • BILLIUM_BASE_URL env
    Override the API base URL (testing / staging environments).

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account BilliumHQ, 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 Crypto & blockchaini

  • More stars than 0% of the other 1614 servers in this category
  • Published to the registry more recently than 23% of the other 1614 servers in this category
  • Basic checks equal to or better than 100% of the other 1614 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 Billium 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: BILLIUM_API_KEY, BILLIUM_MERCHANT_ID

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.3) reached the registry 5 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: Highwire, Crypto Sentiment X402, Crypto MCP Server

Alternatives

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

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

Highwire

Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.

by HigherMaestroGrowing↓ 1.7K/wkUpdated today

Computer or cloud✓ highwire.fun

Crypto Sentiment X402

Crypto news sentiment for 24 coins: label, score and headlines behind it, paid per call via x402

by whatevercat-creatorVery new↓ 61/wkUpdated today

Runs on your computer

Crypto MCP Server

Live cryptocurrency prices and FX rates as agent tools.

by thenextgennexus.comVery newUpdated today

Runs in the cloud✓ thenextgennexus.com

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.

Billium SDKs

Official client libraries for Billium — non-custodial crypto payments, invoices, and webhooks.

Packages

PackageVersionDescription
@billium/nodeNode.js SDK — invoices, webhook signature verification, webhook management
@billium/mcpMCP server — manage invoices and webhooks from Claude, Cursor, and any MCP host

Additional language SDKs will live as siblings under packages/ as they ship.

Quick start

npm install @billium/node
import { Billium } from '@billium/node';

const billium = new Billium({ apiKey: process.env.BILLIUM_API_KEY, merchantId: process.env.BILLIUM_MERCHANT_ID, webhookSecret: process.env.BILLIUM_WEBHOOK_SECRET, });

const invoice = await billium.invoices.create( { name: 'Order #1234', rawAmount: 99.99 }, { idempotencyKey: crypto.randomUUID() }, );

See packages/node/README.md for the full Node.js SDK reference.

Repository layout

.

├── packages/ │ ├── node/ # @billium/node — TypeScript Node.js SDK │ │ ├── src/ # Source │ │ ├── tests/ # Vitest test suite │ │ ├── README.md # Public-facing docs (rendered on npmjs.com) │ │ └── CHANGELOG.md # Per-release notes │ └── mcp/ # @billium/mcp — Model Context Protocol server │ ├── src/ # Server + tool definitions │ ├── tests/ # Vitest in-memory round-trip suite │ └── README.md # Host setup (Claude Code, Cursor, …) └── .github/ ├── workflows/ # CI + release automation ├── ISSUE_TEMPLATE/ # Bug + feature request forms └── CODEOWNERS # Review requirements

Development

This is an npm workspace. Run scripts from the repository root:

npm install        # installs all workspace packages

npm run lint # typechecks every package (src + tests) npm test # runs every package's test suite npm run build # builds every package

To work on a specific package, you can also cd packages/node && npm .

Releasing

Releases are published to npm by GitHub Actions when a v*.*.* tag is pushed:

  1. Bump packages/node/package.json#version and packages/node/src/version.ts#SDK_VERSION to the new version (CI verifies they match).
  2. Add a section to packages/node/CHANGELOG.md describing the changes.
  3. Commit the bump on main.
  4. Tag and push: git tag v1.0.1 && git push origin v1.0.1.
  5. The release workflow runs lint, test, build, then npm publish with provenance.

License

MIT

Ask PopNx