Skip to main content
Glama
Sign In
deenesjakoruzh
Fewsats MCP Server

Fewsats MCP Server

Official
by Fewsats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fewsats-mcp: A Fewsats MCP Server

Overview

This MCP server integrates with Fewsats and allows AI Agents to purchase anything in a secure way.

MCP is

Tools

  1. balance

    • Retrieve the balance of the user's wallet

    • Input: None

    • Returns: Current wallet balance information

  2. payment_methods

    • Retrieve the user's payment methods

    • Input: None

    • Returns: List of available payment methods

  3. pay_offer

    • Pays an offer with the specified ID from the l402_offers

    • Input:

      • offer_id (string): String identifier for the offer

      • l402_offer (object): Offer details containing:

        • offers: Array of offer objects with ID, amount, currency, description, title

        • payment_context_token: Payment context token string

        • payment_request_url: URL for payment request

        • version: API version string

    • Returns: Payment status response

  4. payment_info

    • Retrieve the details of a payment

    • Input:

      • pid (string): Payment ID to retrieve information for

    • Returns: Detailed payment information

Related MCP server: satsrail-mcp

Installation

Using uv (recommended)

When using uv no specific installation is needed. We will use uvx to directly run fewsats-mcp.

uvx fewsats-mcp

Using PIP

Alternatively you can install fewsats-mcp via pip:

pip install fewsats-mcp

After installation, you can run it as a script using:

fewsats-mcp

Configuration

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

Important: Replace YOUR_FEWSATS_API_KEY with the API key you obtained from Fewsats.com.

"mcpServers": {
  "Fewsats Server": {
    "command": "uvx",
    "args": ["fewsats-mcp"],
    "env": {
      "FEWSATS_API_KEY": "YOUR_FEWSATS_API_KEY"
    }
  }
}

Available Tools

6 tools
balanceA

Retrieve the balance of the user's wallet. You will rarely need to call this unless instructed by the user, or to troubleshoot payment issues. Fewsats will automatically add balance when needed.

Inputs: no named parameters.

billing_infoA

Retrieve the user's billing information. Returns billing details including name, address, and other relevant information. This information can also be used as shipping address for purchases.

Inputs: no named parameters.

create_x402_payment_headerB
Creates a payment header for the X402 protocol.

The chain is base-sepolia or base
The x402 payload must be a dict with this structure:
{
    "accepts": [
        {
            "asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
            "description": "Payment for GET https://proxy402.com/7Yhuf2O3zs",
            "extra": {
                "name": "USDC",
                "version": "2"
            },
            "maxAmountRequired": "10",
            "maxTimeoutSeconds": 300,
            "mimeType": "",
            "network": "base-sepolia",
            "payTo": "0xbA5Ae80f48E0C74878c1a362D69c27c2135Aa594",
            "resource": "https://proxy402.com/7Yhuf2O3zs",
            "scheme": "exact"
        }
    ],
    "error": "X-PAYMENT header is required",
    "x402Version": 1
}

Returns a dict with the payment_header field that must be set in X-PAYMENT header in a x402 http request.

Inputs: chain (required), x402_payload (required).

payment_infoB

Retrieve the details of a payment. If payment status is needs_review inform the user he will have to approve it at app.fewsats.com

Inputs: pid (required).

payment_methodsA

Retrieve the user's payment methods. You will rarely need to call this unless instructed by the user, or to troubleshoot payment issues. Fewsats will automatically select the best payment method.

Inputs: no named parameters.

pay_offerB

Pays an offer_id from the l402_offers.

The l402_offer parameter must be a dict with this structure:
{
    'offers': [
        {
            'id': 'test_offer_2',        # String identifier for the offer
            'amount': 1,                 # Numeric cost value
            'currency': 'usd',           # Currency code
            'description': 'Test offer', # Text description
            'title': 'Test Package'      # Title of the package
        }
    ],
    'payment_context_token': '60a8e027-8b8b-4ccf-b2b9-380ed0930283',  # Payment context token
    'payment_request_url': 'https://api.fewsats.com/v0/l402/payment-request',  # Payment URL
    'version': '0.2.2'  # API version
}

Returns payment status response.
If payment status is `needs_review` inform the user he will have to approve it at app.fewsats.com

Inputs: offer_id (required), l402_offer (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes: balance, billing_info, payment_info, and payment_methods are clearly differentiated for wallet, billing, payment details, and payment methods respectively. However, create_x402_payment_header and pay_offer both involve payment processing and could be slightly confusing, as they target different protocols (X402 vs L402) but share overlapping payment-related functionality.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern throughout (e.g., billing_info, payment_methods). However, there is a minor inconsistency with create_x402_payment_header using a more descriptive prefix (create_x402_) while others are simpler nouns or verb_noun combos, slightly deviating from a uniform style.

    Tool Count5/5

    With 6 tools, the count is well-scoped for a payment and wallet management server. Each tool serves a specific function without redundancy, covering key areas like balance, billing, payments, and payment methods, making it efficient and manageable.

    Completeness4/5

    The tool set covers core payment and wallet operations well, including balance retrieval, billing info, payment details, payment methods, and payment execution for different protocols. A minor gap exists in lacking tools for updating or deleting payment methods or billing info, but agents can likely work around this with the provided tools.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • satsrail-mcp

      satsrail-mcpofficial

      SatsRail
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to accept Bitcoin Lightning payments. It allows agents to create orders, generate invoices, check payment status, and manage the full SatsRail merchant API through natural language.
      MIT

    • btc-mcp-srv

      lightphon
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.
      MIT

    Appeared in Searches