PayRam Helper MCP Server

by payram Your server? Claim it

answering

PayRam Helper MCP Server is answering right now. Last checked 5 min ago. It exposes 52 tools. Last commit 25 Jul 2026.

Remote MCP server to integrate and validate self-hosted PayRam deployments.

Uptime history 47 days of history · worst day 31%

47 days agonow

42.0%

Uptime 24h

116 of 276 checks

Tools

read from the server

248 ms

Response time

average over 24h

156

Stars

last commit 25 Jul 2026

PayRam Helper MCP Server does not always answer

Over the last week it answered 36.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

This server publishes 2 more addresses. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 52

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.

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.

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_referral_flow

Detail the referrer/referee lifecycle and required APIs.

explain_referrals_basics

Summarize how Payram referral campaigns are configured and managed.

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 relative to docs/payram-docs-live. Optionally scope by a prefix such as "features".

payram_doctor

Staged, read-only health diagnosis: server reachability -> merchant API key -> admin JWT -> payment readiness (wallets + listener workers). Returns ranked likely causes with exact fix commands for the first failing stage. Run this FIRST when anything PayRam-related fails.

payment

check_payment_readiness

Diagnoses what is NOT yet set up to accept payments, per blockchain: missing deposit wallet, chain/currency not enabled for the project, or a stopped listener worker. Read-only — reports gaps and points to the CLI for wallet setup; it does not create wallets itself.

create_payment_link

Creates a PayRam checkout (payment) link and returns the hosted URL plus a reference_id. Authenticates with the Merchant API-Key (set PAYRAM_API_KEY). This WRITES — it creates a real payment request. The customer chooses the chain/currency on the hosted checkout. Poll status later with lookup_payment (or GET /api/v1/payment/reference/{reference_id}).

get_payment_summary

Returns payment counts: total, open, closed, and cancelled. Useful for a quick overview of payment activity.

agent

get_agent_setup_flow

Returns the step-by-step setup flow for deploying PayRam as an agent. Covers install, wallet creation, faucet funding, contract deployment, and first payment. Includes chain recommendations (ETH Sepolia for testnet, Base for mainnet), faucet URLs, card-to-crypto prerequisites, and status/recovery commands for interrupted sessions.

assess

assess_payram_project

Inspects dependency files, frameworks, and .env status to suggest the next integration actions.

currencies

list_currencies

Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Public endpoint — works with only PAYRAM_BASE_URL set, no API key or JWT required. Use this to discover valid blockchainCode/currencyCode values before creating payments or payouts.

daily

get_daily_volume

Returns the total payment volume for a given date, with breakdowns by network and currency. Only counts FILLED (completed) payments. Defaults to today if no date is specified.

lookup

lookup_payment

Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID. Returns up to 5 matching payments with full details.

node

check_node_sync

Per-chain node health verdict: healthy / lagging / unreachable / listener-down. Computes how old each RPC node’s last block is — any non-BTC chain older than 10 minutes (BTC: 90 minutes, since BTC blocks every ~10m) is flagged as lagging or not syncing. Also checks the chain’s listener worker. When something is wrong it names the exact remediation (usually restart_payram_worker). Read-only — run this first; restart second; re-run this ~60s after a restart to confirm recovery.

onboard

onboard_agent_setup

Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction.

payments

search_payments

Search and filter payments with full control over status, network, currency, dates, webhook status, and pagination. Returns a paginated list of matching payments.

platforms

list_platforms

Lists all external platforms (projects) for the authenticated user. Use this to discover your platform ID, which other tools auto-resolve if omitted.

prepare

prepare_payram_test

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

recipients

list_recipients

Lists saved withdrawal recipients (payout beneficiaries). Use this to find a recipient ID for the 3-step payout flow, or to check whether a beneficiary is already OTP-verified (status "active") before creating a payout.

referral

get_referral_dashboard_guide

Explain how to embed and manage the referral dashboard experience.

restart

restart_payram_worker

REMEDIATION ACTION (write): restarts a blockchain listener worker via supervisor — the minimal fix when check_node_sync reports a chain as lagging or listener-down. Workflow: run check_node_sync first → restart the named worker → wait ~60s → run check_node_sync again to confirm recovery. A restart does NOT fix an unreachable RPC (fix the RPC config in the dashboard instead). Requires admin JWT with write_system_settings.

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

Checks the /api/v1/payment endpoint on a Payram server using baseUrl and apiKey. If they are not provided, returns a .env template you can add to your workspace.

unswept

get_unswept_balances

Returns unswept (unsettled) balances across all wallets, broken down by blockchain and currency. Shows sweep readiness per entry (sweep, sweep_in_progress, sweep_not_allowed, no_balance) AND why stuck funds are stuck: lastSweepError (e.g. HOT_WALLET_LOW_GAS with the hot-wallet address to fund), pending SCW deployment, or missing cold wallet. Use this to answer "where is my money / why has it not swept".

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.payram.com/	streamable-http	answering	52 ms	5 min ago
https://mcp.payram.com/mcp	streamable-http	answering	285 ms	5 min ago
https://mcp.payram.com/mcp/sse	sse	answering	250 ms	6 min ago

Alternatives to PayRam Helper MCP Server

same job, measured the same way

Umami Compass

by webcredo

Secure Umami Analytics MCP server for Cloud and self-hosted deployments

78 installs/wk local only

Vercel Deployment MCP

by addiplus

Reference MCP stdio server for observing Vercel projects and deployments.

68 installs/wk local only

Runcomfy MCP

by runcomfy-com

Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools.

10 tools answering

Remote Bridge

by varaprasadreddy9676

Sync code to remote servers via SSH/rsync and deploy from any AI IDE.

51 installs/wk local only

Zoxron MCP

by zoxron

Your AI agent deploys, migrates & upgrades self-hosted Odoo ERP on a server you own.

answering

InsForge

by insforge

MCP server for InsForge BaaS — database, storage, edge functions, and deployments

461 installs/wk answering

CloudPepper

by cloudpepper

Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.

answering

Alpic

by alpic-mcp

Manage your projects, debug deployments, and check analytics for any MCP server you host with Alpic.

answering

PayRam Helper MCP Server — questions

Answers built from our own checks of this server.

What can PayRam Helper MCP Server do?

It exposes 52 tools, read directly from the server on our last check. Among them: assess_payram_project, check_node_sync, check_payment_readiness, create_payment_link, explain_payment_flow, explain_payram_basics and 46 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 Helper MCP Server mostly used for?

Its tools cluster around generate, snippet and explain. 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 Helper MCP Server working right now?

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

How do I connect PayRam Helper MCP Server?

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

Does PayRam Helper MCP Server need an API key?

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

How fast is PayRam Helper MCP Server?

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

Is PayRam Helper MCP Server open source?

We cannot say either way: written in TypeScript, 156 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.