@three-ws/ibm-x402-mcp
Enables pay-per-use AI model calls with USDC micropayments settled on the Solana blockchain.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@three-ws/ibm-x402-mcpwrite a Python script to download a web page"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol server that exposes IBM Granite foundation models as pay-per-use tools via the x402 payment protocol. End users pay USDC on Solana per call — no IBM Cloud account of their own. The server operator supplies IBM credentials (
WATSONX_*) and a receiving Solana wallet (MCP_SVM_PAYMENT_ADDRESS); callers supply only USDC. One free tool (ibm_granite_getting_started) explains prices and the flow before any payment.
Built by three.ws. Community-built and not affiliated with IBM.
How it works
An MCP client (Claude Desktop, Claude Code, Cursor, or an agent) connects to this server.
The client calls a tool — e.g.
ibm_granite_chat.Without an x402 payment payload, the server returns a
402 PaymentRequiredenvelope quoting the USDC price and the Solana receiving address.The client signs a Solana USDC transfer and retries with the payment in
_meta["x402/payment"].The server verifies and settles the payment via the facilitator, calls IBM watsonx.ai, and returns the result with a settlement receipt in
_meta["x402/payment-response"].
x402-capable MCP clients handle this loop automatically.
Related MCP server: maxia-mcp
Install
npm install @three-ws/ibm-x402-mcpRun it directly with npx (no install needed):
MCP_SVM_PAYMENT_ADDRESS=<your-solana-wallet> \
WATSONX_API_KEY=<ibm-api-key> \
WATSONX_PROJECT_ID=<watsonx-project-id> \
npx @three-ws/ibm-x402-mcpOr install globally for the ibm-x402-mcp binary on your PATH:
npm install -g @three-ws/ibm-x402-mcpQuick start
With Claude Code, one command (as an end user paying per call, no env vars needed):
claude mcp add ibm-granite-x402 -- npx -y @three-ws/ibm-x402-mcpServer operators add -e MCP_SVM_PAYMENT_ADDRESS=... -e WATSONX_API_KEY=... -e WATSONX_PROJECT_ID=... before the --.
Or wire the server into your MCP client config (claude_desktop_config.json, Cursor's mcp.json):
{
"mcpServers": {
"ibm-x402": {
"command": "npx",
"args": ["-y", "@three-ws/ibm-x402-mcp"],
"env": {
"MCP_SVM_PAYMENT_ADDRESS": "your-solana-wallet-address",
"WATSONX_API_KEY": "your-ibm-cloud-api-key",
"WATSONX_PROJECT_ID": "your-watsonx-project-id"
}
}
}
}Inspect the tool surface with the MCP Inspector:
npx -y @modelcontextprotocol/inspector npx @three-ws/ibm-x402-mcpTools
Tool | What it does | Price |
| Overview, prices, and the x402 payment flow. No payment or IBM account required. | Free |
| Conversational AI via IBM Granite (default | $0.02 USDC |
| Code generate, review, refactor, explain, test, document. | $0.025 USDC |
| Batch text embeddings for RAG, search, and clustering (1–64 texts). | $0.005 USDC |
| Structured document analysis: entities, sentiment, risk flags, summary, next steps. | $0.04 USDC |
| Zero-shot time-series forecasting via IBM Granite TTM (Tiny Time Mixer). | $0.05 USDC |
Every tool is a read-only model-inference call — nothing on your machine or in any account is modified — and declares MCP tool annotations (readOnlyHint, openWorldHint, idempotentHint) so clients can reason about side effects before paying.
Input parameters
ibm_granite_chat — messages (required: 1–50 { role, content } pairs), model, max_new_tokens (1–4096, default 1024), temperature (0–2, default 0.7).
ibm_granite_code — task (required: generate/review/refactor/explain/test/document), prompt (required), language, context.
ibm_granite_embed — inputs (required: 1–64 texts, ≤8000 chars each), model.
ibm_granite_analyze — document (required), analysis_type (general/contract/financial/technical/medical/sentiment, default general), language.
ibm_granite_forecast — timestamps (required: 64–1024 ISO-8601, uniform cadence, oldest first), values (required: 64–1024 numbers, same length), freq (required: pandas cadence, e.g. 1h, 1D), prediction_length (1–96), label.
Example calls
// ibm_granite_chat
{
"messages": [
{ "role": "system", "content": "You are an expert data engineer." },
{ "role": "user", "content": "Design a lakehouse schema for IoT sensor telemetry." }
],
"max_new_tokens": 1024,
"temperature": 0.7
}
// ibm_granite_code
{ "task": "review", "prompt": "def calculate_roi(revenue, cost): return revenue / cost", "language": "Python" }
// ibm_granite_embed
{ "inputs": ["enterprise data governance", "cloud-native AI pipeline", "real-time analytics"] }
// ibm_granite_analyze
{ "document": "This Software License Agreement is entered into between...", "analysis_type": "contract" }
// ibm_granite_forecast (timestamps/values must be 64–1024 points; abbreviated here)
{ "timestamps": ["2025-01-01T00:00:00Z", "...", "2025-03-05T00:00:00Z"], "values": [12500, "...", 13200], "freq": "1D", "prediction_length": 14, "label": "daily_revenue_usd" }Payment flow
This server uses the x402 protocol for micropayments:
Client calls a tool without payment →
402 PaymentRequiredwith the USDC amount and Solana address.Client builds and signs a Solana USDC transfer transaction.
Client retries with the signed tx in
_meta["x402/payment"].Server verifies and settles via the configured facilitator (default PayAI).
Server calls IBM watsonx.ai and returns the result with
_meta["x402/payment-response"](settlement receipt).
MCP Client (Claude Desktop / Cursor / agent)
│ tools/call (with x402 payment in _meta)
▼
ibm-x402-mcp (stdio MCP server)
│ verify + settle USDC on Solana
├──► x402 facilitator (default https://facilitator.payai.network)
│
│ inference call with IAM Bearer token
└──► IBM watsonx.ai (us-south.ml.cloud.ibm.com)
└── IBM Granite 3 8B Instruct / Embedding / TTMRequirements
Node.js >= 20.
A Solana wallet address to receive USDC (
MCP_SVM_PAYMENT_ADDRESS).IBM Cloud credentials: an API key (create one) and a watsonx.ai project id (Project → Manage → General → Project ID), or a deployment space id.
Environment variables
Variable | Required | Default |
| yes | — |
| yes | — |
| yes (or | — |
| alternative to | — |
| no |
|
| no |
|
| no |
|
| no | three.ws fee payer |
| no |
|
Regional hosts: us-south, eu-de, eu-gb, jp-tok, au-syd, ca-tor — e.g. https://eu-de.ml.cloud.ibm.com.
Related
@three-ws/ibm-watsonx-mcp— the same IBM Granite tools driven by your own IBM Cloud credentials (no x402, no per-call payment).
Links
Homepage: https://three.ws
Changelog: https://three.ws/changelog
License: Apache-2.0 — see LICENSE
License
Copyright © 2026 nirholas. All rights reserved.
This software is proprietary — see LICENSE. No rights are granted without the express written permission of the copyright owner.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nirholas/ibm-x402-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server