X402 Services vs Goldbean
A side-by-side look at the X402 Services and Goldbean MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose X402 Services for finance & fintech work over a hosted endpoint; choose Goldbean for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose X402 Services when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
markdown, extract, read.
Choose Goldbean when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
fetch, get_balance, list_accounts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 53/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 159 | 12 |
| Full listing | View X402 Services | View Goldbean |
Tools & capabilities
X402 Services tools 159
markdownConvert raw HTML to clean, LLM-ready markdown. Strips nav/script/style noise. [x402 paid tool — price $0.003; POST /api/markdown]extractExtract structured data (title, links, meta, headings, text) from HTML as JSON. [x402 paid tool — price $0.003; POST /api/extract]readFetch any public web page and return clean, LLM-ready markdown (plus title and final URL). Send { url }. We handle fetching, redirects, and noise-stripping. [x402 paid tool — price $0.003; POST /api/read]read_structuredFetch any public web page and return structured JSON: title, meta description, headings, links, text preview. Send { url }. [x402 paid tool — price $0.003; POST /api/read/structured]memory_setAgent Memory: durable key-value storage that survives between agent runs. Write a JSON value (16KB max) under a key. First write to a namespace claims it with your secret token. Send { ns, token, key, value }. [x402 paid tool — price $0.003; POST /api/memory/set]memory_getAgent Memory: read a stored value by key, or omit key to list all keys in your namespace. Send { ns, token, key? }. [x402 paid tool — price $0.003; POST /api/memory/get]scheduleWebhook Scheduler: schedule a future HTTP callback. At fireAt, we call your url with the payload. Agents' alarm clock for async work. Send { token, url, fireAt (ISO-8601), payload?, method? }. [x402 paid tool — price $0.003; POST /api/schedule]schedule_statusWebhook Scheduler: check a scheduled job's status and last delivery result. Send { token, id }. [x402 paid tool — price $0.003; POST /api/schedule/status]counterAtomic counter: increment-and-return a named counter (collision-free running totals & IDs across agent runs). Send { name, token, by? }. [x402 paid tool — price $0.003; POST /api/counter]lock_acquireDistributed lock: acquire a named lock for ttlSec so only one agent proceeds. Returns acquired:false if held. Send { name, token, ttlSec? }. [x402 paid tool — price $0.003; POST /api/lock/acquire]lock_releaseRelease a distributed lock you hold. Send { name, token, holder? }. [x402 paid tool — price $0.003; POST /api/lock/release]queue_pushTask queue: append a JSON item to a named queue for later/other agents. Send { name, token, item }. [x402 paid tool — price $0.003; POST /api/queue/push]- +147 more on the listing page
Goldbean tools 12
fetchHTTP fetch with automatic authentication and payment handling. Makes the request, retries with SIGN-IN-WITH-X when the route exposes a SIWX challenge, and only pays if the route still returns 402. Returns response data and the final response headers, including raw payment receipt proof when supplied by the server, along with payment details (price, tx hash) if a payment was made. For endpoints you haven't called before in this session, you MUST call check_endpoint_schema first to confirm the request body schema. Skipping this causes 400 errors from wrong field names.get_balanceGet your total USDC balance across all supported networks. Auto-creates the wallet on first use (~/.agentcash/wallet.json). Use this before paid API calls to confirm you have funds available.list_accountsList wallet accounts for each supported network. Returns the network, address, balance, and deposit link for every supported network so you can see where to fund the wallet. Auto-creates the wallet on first use (~/.agentcash/wallet.json). If onboardingCta is present, show its message to the user — it means they haven't onboarded yet and need to either visit the onboard link or deposit directly.check_endpoint_schemaGet the input/output schema and auth mode (paid or SIWX) for a single endpoint. Call this to see exactly what fields the request body expects and what the response contains. Returns the schema from the origin's OpenAPI spec. Optionally pass sample_input_body to probe the endpoint live (without payment) for an exact price quote — do this when pricing is dynamic (range-based or variable), or when you're unsure about the input schema. Treat auth mode as advisory: fetch handles both SIWX and paid routes.redeem_inviteRedeem an invite code for free USDC on Base. One-time use per code. Returns amount received and transaction hash. Use get_balance after to verify funds, or list_accounts if you need the per-network deposit links as well.discover_api_endpointsList available endpoints at an API origin. Returns endpoint URLs with descriptions of what each does and the auth mode for each (paid or SIWX). Works with any origin, not just the registered ones. Call this when you need to see what routes are available at an origin — whether it's one of the registered origins or any other origin you've identified as useful. Treat the auth mode as guidance for what the route may require; fetch handles both SIWX and payment. The response always indicates whether guidance is available. Guidance is documentation published by the API provider explaining how endpoints work together, edge cases, and usage tips. compact guidance is included automatically; set include_guidance=true to force-include full usage documentation when you need to compose two or more endpoints or need clarification on how the origin works.report_errorEMERGENCY ONLY. Report critical MCP tool bugs. Do NOT use for normal errors (balance, network, 4xx) — those are recoverable.update_settingsUpdate user settings (persisted to ~/.agentcash/settings.json). Currently supports maxAmount — the maximum USD amount allowed per fetch request. If a fetch response requests more than this, the payment is rejected. Returns the current settings after applying changes.get_settingsGet current user settings. Returns persisted values from ~/.agentcash/settings.json with defaults applied.bridgeBridge USDC between supported networks using the current wallet. Requires a source network, destination network, and amount. Use this when funds are on one supported network and the user needs them moved to another. Bridging is subject to fees.searchSearch for relevant paid API services by describing what you need in natural language. Returns the best matching origins with endpoint details and pricing. The top result includes the full input/output schema so you can call it immediately via fetch. Only use this when you DON'T already know which registered origin to use. If the task clearly maps to a registered origin (e.g. people search → StableEnrich, image generation → StableStudio), skip search and go straight to discover_api_endpoints on that origin. Search is for discovering NEW or UNKNOWN capabilities outside the registered origins. Set broad=true to widen the search to include newer, unvetted tools that may not have established trust. Use this if the default results don't cover what you need.sessions_closeClose an MPP `tempo:session` payment channel. Pass the channelId surfaced in a prior fetch's paymentInfo together with the same URL you originally fetched. Signs a close credential with the on-chain settled cumulative amount and POSTs it to the server, returning the on-chain settlement transaction hash when available. Use this when you want to finalize a channel rather than leaving it open for the server to settle on its own schedule.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
X402 Services
{
"mcpServers": {
"x402-services": {
"url": "https://x402-services-production.up.railway.app/mcp"
}
}
}
Goldbean
{
"mcpServers": {
"wuzenghai616-lang-goldbean": {
"command": "npx",
"args": [
"-y",
"agentcash@latest"
]
}
}
}
Frequently asked questions
X402 Services is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Goldbean belongs to Finance & Fintech and uses a local stdio subprocess. Pick X402 Services for finance & fintech work and Goldbean for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
X402 Services has no declared pricing — check the project's own site. Goldbean is listed as freemium — a free tier with paid plans. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add x402-services and wuzenghai616-lang-goldbean as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, X402 Services has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Goldbean has 63/100 (Good) with 3 views, 0 installs and 1 GitHub stars.