Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAYFETCH_VIANoOptional via= attribution slug sent on guard calls only.
PAYFETCH_APPROVERNo1 grants approval authority. Refused with a queue-capable mode.
PAYFETCH_DATA_DIRNoLedger, state, and config root. Default ~/.payfetch.
PAYFETCH_KEY_FILENoPath to a mode-600 file holding a 0x-hex key.
PAYFETCH_TEST_MODENoAny value marks receipts test:true and refuses Base mainnet quotes (Sepolia only).
PAYFETCH_PRIVATE_KEYNo0x-hex EVM private key.
PAYFETCH_CDP_API_KEY_IDNoCoinbase CDP API key ID.
PAYFETCH_CDP_ACCOUNT_NAMENoOptional named CDP EVM account. Defaults to a stable name.
PAYFETCH_CDP_WALLET_SECRETNoCoinbase CDP wallet secret.
PAYFETCH_CDP_API_KEY_SECRETNoCoinbase CDP API key secret.

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
paid_fetchA

Fetch a URL, automatically paying if it requires payment (HTTP 402, x402 protocol) — within the operator's spending policy. Free URLs are fetched normally at no cost. Use payment_quote first if you only want to know the price. Payments above the operator's approval threshold will ask the human for confirmation. Spending policy is operator-owned config; no tool can widen it.

payment_quoteA

Check what a paid URL costs and whether the current spending policy would allow paying it, WITHOUT paying. Returns the price, payment terms, trust-check results, and the policy decision. Spending policy is operator-owned config; no tool can widen it.

spend_statusA

Show today's agent spending: totals, remaining budgets overall and per host, active holds, and recent payments. Spending policy is operator-owned config; no tool can widen it.

list_receiptsA

Query the local payment receipt ledger (audit trail). Filter by time, host, or outcome. Spending policy is operator-owned config; no tool can widen it.

approve_pendingB

List or resolve payments waiting for human approval (queue mode). Approving grants a one-time re-run permission for that exact payment. It only resolves payments already queued for approval; it cannot change spending policy — no payfetch tool can widen operator-owned limits.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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/forum-labs/payfetch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server