Skip to main content
Glama
Token4uAi

token4u-mcp

Official
by Token4uAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TOKEN4U_API_URLNotoken4u API base URLhttps://token4u.ai
TOKEN4U_DATA_DIRNoDirectory for wallet key and session storage~/.token4u-mcp
TOKEN4U_WALLET_KEYNoLocal wallet private key (takes priority over file)
TOKEN4U_BUDGET_LIMITNoMax USD budget for LLM calls

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
token4u_walletA

Manage local x402 wallet — create keypair, check status, and get funding guidance.

This is a pure external x402 mode: the MCP server manages a local wallet (~/.token4u-mcp/wallet.json, 0o600). All payments go through on-chain x402 USDC transactions on Base network. No token4u account or internal wallet required.

Actions:

  • status (default): Show local wallet address and whether it is newly created.

  • create: Generate a new local wallet keypair or load an existing one. The private key is stored at ~/.token4u-mcp/wallet.json with 0o600 permissions and never leaves this machine.

  • setup: Show step-by-step funding instructions — how to send USDC on Base to your local wallet address, and how to export the private key for self-custody.

token4u_chatA

Chat with AI models via token4u using x402 micropayments (USDC on Base). Each call is priced per-model and paid via an EIP-3009 authorization from your local wallet. Requires a wallet — run token4u_wallet action=create first.

token4u_consumptionA

Query x402 consumption records for a given EVM wallet address. Public API — no login required. Returns per-call records with model, token usage, credits, amount paid in USD, transaction hash, and timestamp.

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

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: wallet management, chat with micropayments, and consumption record querying. There is no overlap or ambiguity between them; even the actions within token4u_wallet are well-separated.

Naming Consistency5/5

All tool names follow the consistent pattern 'token4u_<noun>' using snake_case. This makes the toolset predictable and easy to navigate for agents.

Tool Count5/5

With only 3 tools, the server is tightly scoped to its purpose of handling x402 micropayments via a local wallet. Each tool provides a distinct and necessary function, and none feel redundant or superfluous.

Completeness4/5

The set covers the full workflow: wallet creation/funding guidance, chat with micropayments, and transaction consumption queries. A minor gap is the lack of a direct balance-check tool, but the core functionality is complete for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources