PayRam MCP Server

by payram Your server? Claim it

not responding

PayRam is listed as active in the registry but did not answer our last check. It exposes 44 tools. Last commit 26 Oct 2026.

Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.

Uptime history 26 days of history · worst day 0%

26 days agonow

67.0%

Uptime 24h

61 of 91 checks

Tools

read from the server

212 ms

Response time

average over 24h

158

Stars

last commit 26 Oct 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

13 Oct 6 tool descriptions were rewritten get_agent_setup_flow, list_payram_docs, onboard_agent_setup and 3 more

13 Oct 3 tools changed the parameters they ask for payram_doctor, payram_runbook, payram_setup_plan

13 Oct 2 tools appeared explain_payram_security, payram_troubleshoot

What the code does

We read the source, 6 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable src/tools/context/docById.ts:36, src/utils/markdownLoader.ts:14

  const fullPath = path.join(docsRoot, relativePath);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.payram.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.payram.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.payram.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.payram.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.payram.com/mcp"
    }
  }
}

Available tools 44

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

generate

generate_env_template

Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.

generate_mock_webhook_event

Generates a snippet to send mock Payram webhook events to your local endpoint for testing.

generate_payment_http_snippet

Generates a raw HTTP sample for creating a Payram payment in the requested language.

generate_payment_route_snippet

Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.

generate_payment_sdk_snippet

Generates backend code using the official Payram JS/TS SDK to create a payment.

generate_payment_status_snippet

Generates backend code to query the status of a Payram payment.

generate_payout_recipient_flow_snippet

Generates the recommended OTP-verified payout flow: create recipient → validate OTP → create payout against the saved recipient. Use this for repeat beneficiaries; use generate_payout_sdk_snippet for one-off direct payouts.

generate_payout_sdk_snippet

Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.

generate_payout_status_snippet

Generates backend code to query the status of a payout using the Payram SDK.

generate_referral_route_snippet

Generates a backend route such as /api/referrals/create for logging referral events.

generate_referral_sdk_snippet

Generates a backend route or service snippet to create a referral event using the Payram SDK.

generate_referral_status_snippet

Generates code to fetch referral progress, rewards, or status.

generate_referral_validation_snippet

Generates a snippet to validate referral IDs, statuses, and eligibility.

generate_setup_checklist

Returns a step-by-step checklist of everything a merchant must configure to start using Payram.

generate_topup_integration_snippet

For EXISTING apps: emits the recommended top-up wallet integration — ledger schema + cumulative-credit webhook handler + atomic invoice-settle function. Credits crypto payments to a user's balance first, then debits invoices from it, so over/under/late/duplicate payments become balance states, not payment exceptions. Pair with the payram-topup-wallet-integration skill. (New store with no users? Use the checkout/plugin path instead.)

generate_webhook_event_router

Generates a backend event router that dispatches Payram webhook events to domain handlers.

generate_webhook_handler

Generates backend code to handle Payram webhook HTTP requests.

payram

get_payram_doc_by_id

Returns the markdown for a Payram doc given its id, e.g. "features/payouts".

get_payram_links

Surface official documentation, website, and community links.

list_payram_docs

Lists the available Payram doc ids. Optionally scope by a prefix such as "features".

payram_doctor

Read-only diagnosis of a PayRam server by its public URL — works from the hosted MCP without credentials: reachability, health, TLS certificate, installed vs latest version, worker states. Optionally validates an API key without creating anything. Returns ranked likely causes and exact fixes for the first failing stage. Run this first when anything PayRam-related fails.

payram_ops_playbook

Exact, copy-paste recipes for day-2 operations and troubleshooting that YOU run against the merchant's PayRam API with credentials that stay on your machine: which endpoint, which credential (public / dashboard JWT / project API key), a curl+jq command, how to read the answer, and what not to do. Start with "connect". Tasks: connect, health, version_check, workers, restart_worker, node_sync, site_url, payment_options, unswept_funds, payments_today, payment_lookup, stuck_payment, create_payment_link, payouts, webhooks, logs, daily_check. Omit task to list them.

payram_runbook

Step-by-step procedures for changes to a running PayRam, each step marked agent vs human with hard stops: set_site_url, change_domain, ssl_setup, ssl_renewal_fix, firewall_ports, upgrade, backup, restore, add_chain, smart_bridge, mainnet_cutover, operator_setup, rotate_api_key, reset_test_install, shopify_connector, woocommerce_plugin, secure_analytics_mcp, install_failed, custom_port_or_proxy, external_database, forgot_root_password. Omit task to list them.

payram_setup_plan

Start here to install PayRam on a VPS. Returns an ordered, personalised plan — prepare server → install → claim admin + set public URL → wallets (incl. Smart Bridge review) → API key + first payment link → hardening → store/app integration — with who runs each step (agent shell vs human/dashboard), exact commands, what success looks like, and hard stops that need the human (cold wallet, mainnet spend, root-only settings). Ask the user first whether you can run commands on their server (access "ssh") or only chat with them (access "human_runs_commands": they run each command and paste the output back). Pass stage to resume mid-way; payram_doctor tells you the stage of a running server.

payram_troubleshoot

Something is not working? Describe the problem in plain words and/or paste the error or log text. Returns the known PayRam problems it matches, what each usually means, how to confirm it and the fix, plus which tool to use next. Needs no credentials and no access to the server; what you paste is not stored. Call with nothing to list known problems. For a live check of a running server use payram_doctor.

explain

explain_payment_flow

Describe how payments move from customer initiation through settlement.

explain_payram_basics

Explain Payram's product pillars, architecture, payments, and payouts capabilities.

explain_payram_concepts

Glossary-backed explanation of Payram terminology and constraints.

explain_payram_security

Answer "is PayRam safe / trustworthy / audited?": why an agent can use it without holding secrets, the independent smart contract audit (what it covers and what it does not), and how to verify the report.

explain_referral_flow

Detail the referrer/referee lifecycle and required APIs.

explain_referrals_basics

Summarize how Payram referral campaigns are configured and managed.

snippet

snippet_express_payment_route

Returns an Express router that posts to Payram's /api/v1/payment endpoint.

snippet_fastapi_payment_route

Returns a FastAPI handler that calls Payram's create-payment HTTP API.

snippet_go_payment_handler

Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.

snippet_laravel_payment_route

Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.

snippet_nextjs_payment_route

Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.

snippet_spring_payment_controller

Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.

agent

get_agent_setup_flow

Returns the canonical PayRam headless-agent guide: agent CLI commands, env vars, merchant vs operator mode, wallet flows, adding chains, troubleshooting. Long (~11k tokens). For a short personalised plan use payram_setup_plan.

onboard

onboard_agent_setup

Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).

prepare

prepare_payram_test

Confirm hosting, credentials, and environment variables before generating demo apps.

referral

get_referral_dashboard_guide

Explain how to embed and manage the referral dashboard experience.

scaffold

scaffold_payram_app

Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.

suggest

suggest_file_structure

Suggests a recommended backend folder/file structure for integrating Payram.

test

test_payram_connection

Deprecated: use payram_doctor, which does this and more. Read-only check that a PayRam server is reachable and healthy and, if an API key is supplied, that the key is accepted. Never creates payments.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.payram.com/mcp	streamable-http	answering	45 ms	12 min ago

Alternatives to PayRam

same job, measured the same way

Yault AESP

by yault

Crypto payments for the agent economy — policy-gated vault operations under human control

34 installs/wk local only

Spraay X402 MCP

by plagtech

MCP server for Spraay x402 Gateway. 60 tools for crypto payments, DeFi, and AI on Base.

39 installs/wk local only

Toreador

by toreador

Generate crypto QR codes (BTC, ETH, SOL, USDC, USDT, EURC) and manage payment sessions.

66 installs/wk local only

Eustore

by aibollingmo

S3-compatible European object storage for AI agents. GDPR-compliant, EU-hosted, crypto payments.

75 installs/wk local only

Cartography MCP Server

by mrcartographer

Human-curated crypto market intelligence with x402 payments. Weekly signals and analysis.

71 installs/wk local only

Voulti

by csacanam

Accept crypto payments from AI agents: invoices + hosted checkout on 5 chains. No API key.

42 installs/wk local only

AgentPay VN

by phuocdu

Let AI agents collect VietQR payments — generate a QR and auto-confirm settlement.

196 installs/wk local only

Billium

by billiumhq

Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.

54 installs/wk local only

PayRam — questions

Answers built from our own checks of this server.

What can PayRam do?

It exposes 44 tools, read directly from the server on our last check. Among them: explain_payment_flow, explain_payram_basics, explain_payram_concepts, explain_payram_security, explain_referral_flow, explain_referrals_basics and 38 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is PayRam mostly used for?

Its tools cluster around generate, payram and snippet. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is PayRam working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 61 of 91 checks got a reply (67.0%), average response time 212 ms. The bar chart above shows every period we have measured.

The registry lists PayRam as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect PayRam?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does PayRam need an API key?

No. PayRam completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 44 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is PayRam?

It answers our handshake in 212 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is PayRam open source?

We cannot say either way: written in TypeScript, 158 stars on GitHub and 3 open issues, but we could not determine the licence, and without one the code is not open source by default.