Skip to main content
Glama
Fewsats

Fewsats MCP Server

Official
by Fewsats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

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

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.

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

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.

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

ActivityInactive
ResponsivenessNo issues

Resources