Highwire
Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.
Description from the maker (original English)
Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
BILLIUM_API_KEY, BILLIUM_MERCHANT_ID, BILLIUM_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
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/mcpFill in the empty values before running it.
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.
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.
BILLIUM_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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 8, 2026
The registry name was verified with the GitHub account BilliumHQ, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
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
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: BILLIUM_API_KEY, BILLIUM_MERCHANT_ID
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 –, and the latest version (0.1.3) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Highwire, Crypto Sentiment X402, Crypto MCP Server
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
Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.
Crypto news sentiment for 24 coins: label, score and headlines behind it, paid per call via x402
Live cryptocurrency prices and FX rates as agent tools.
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.
Official client libraries for Billium — non-custodial crypto payments, invoices, and webhooks.
| Package | Version | Description |
|---|---|---|
@billium/node | Node.js SDK — invoices, webhook signature verification, webhook management | |
@billium/mcp | MCP server — manage invoices and webhooks from Claude, Cursor, and any MCP host |
Additional language SDKs will live as siblings under packages/ as they ship.
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.
.
├── 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
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 .
Releases are published to npm by GitHub Actions when a v*.*.* tag is pushed:
packages/node/package.json#version and packages/node/src/version.ts#SDK_VERSION to the new version (CI verifies they match).packages/node/CHANGELOG.md describing the changes.main.git tag v1.0.1 && git push origin v1.0.1.npm publish with provenance.MIT