forum-labs/payfetch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYFETCH_VIA | No | Optional via= attribution slug sent on guard calls only. | |
| PAYFETCH_APPROVER | No | 1 grants approval authority. Refused with a queue-capable mode. | |
| PAYFETCH_DATA_DIR | No | Ledger, state, and config root. Default ~/.payfetch. | |
| PAYFETCH_KEY_FILE | No | Path to a mode-600 file holding a 0x-hex key. | |
| PAYFETCH_TEST_MODE | No | Any value marks receipts test:true and refuses Base mainnet quotes (Sepolia only). | |
| PAYFETCH_PRIVATE_KEY | No | 0x-hex EVM private key. | |
| PAYFETCH_CDP_API_KEY_ID | No | Coinbase CDP API key ID. | |
| PAYFETCH_CDP_ACCOUNT_NAME | No | Optional named CDP EVM account. Defaults to a stable name. | |
| PAYFETCH_CDP_WALLET_SECRET | No | Coinbase CDP wallet secret. | |
| PAYFETCH_CDP_API_KEY_SECRET | No | Coinbase CDP API key secret. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- 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/forum-labs/payfetch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server