PayRam Helper is an MCP server with 52 tools an agent can call, among them assess_payram_project, check_node_sync, check_payment_readiness. It answers at https://mcp.payram.com/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 20 October 2026, succeeded.
Remote MCP server to integrate and validate self-hosted PayRam deployments.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
assess_payram_project | Inspects dependency files, frameworks, and .env status to suggest the next integration actions. |
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 |
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 Inputs: externalPlatformId |
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 Inputs: amountInUSD, customerID, customerEmail |
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. |
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. Inputs: language, status |
generate_payment_http_snippet | Generates a raw HTTP sample for creating a Payram payment in the requested language. Inputs: language |
generate_payment_route_snippet | Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment. Inputs: framework |
generate_payment_sdk_snippet | Generates backend code using the official Payram JS/TS SDK to create a payment. Inputs: framework |
generate_payment_status_snippet | Generates backend code to query the status of a Payram payment. Inputs: style |
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. Inputs: framework |
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. Inputs: framework |
generate_referral_sdk_snippet | Generates a backend route or service snippet to create a referral event using the Payram SDK. Inputs: framework |
generate_referral_status_snippet | Generates code to fetch referral progress, rewards, or status. Inputs: style |
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 ove Inputs: part, framework |
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. Inputs: framework |
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), fauce |
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. Inputs: date, externalPlatformId |
get_payment_summary | Returns payment counts: total, open, closed, and cancelled. Useful for a quick overview of payment activity. Inputs: externalPlatformId |
get_payram_doc_by_id | Returns the markdown for a Payram doc given its id, e.g. "features/payouts". Inputs: id |
get_payram_links | Surface official documentation, website, and community links. |
get_referral_dashboard_guide | Explain how to embed and manage the referral dashboard experience. |
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. H |
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 val |
list_payram_docs | Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as "features". Inputs: prefix |
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. |
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. |
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. Inputs: query, externalPlatformId |
onboard_agent_setup | Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction. |
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 whe Inputs: baseUrl, apiKey |
prepare_payram_test, restart_payram_worker, scaffold_payram_app, search_payments, snippet_express_payment_route, snippet_fastapi_payment_route, snippet_go_payment_handler, snippet_laravel_payment_route, snippet_nextjs_payment_route, snippet_spring_payment_controller, suggest_file_structure, test_payram_connection
Every block below points at https://mcp.payram.com/. Pick your client and copy.
claude mcp add --transport http payram-helper https://mcp.payram.com/
{
"mcpServers": {
"payram-helper": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.payram.com/"]
}
}
}{
"mcpServers": {
"payram-helper": {
"url": "https://mcp.payram.com/"
}
}
}{
"servers": {
"payram-helper": {
"type": "http",
"url": "https://mcp.payram.com/"
}
}
}{
"context_servers": {
"payram-helper": {
"url": "https://mcp.payram.com/"
}
}
}{
"mcpServers": {
"payram-helper": {
"serverUrl": "https://mcp.payram.com/"
}
}
}{
"mcpServers": {
"payram-helper": {
"url": "https://mcp.payram.com/"
}
}
}name: PayRam Helper
version: 0.0.1
schema: v1
mcpServers:
- name: PayRam Helper
type: streamable-http
url: https://mcp.payram.com/{
"mcpServers": {
"payram-helper": {
"httpUrl": "https://mcp.payram.com/"
}
}
}{
"mcpServers": {
"payram-helper": {
"type": "http",
"url": "https://mcp.payram.com/"
}
}
}{
"mcpServers": {
"payram-helper": {
"url": "https://mcp.payram.com/"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.payram.com%2F&type=streamable_http&id=payram-helper&name=PayRam%20Helper
It answered our last check on 20 October 2026 in 334 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
52, as returned by the server's own tools/list on 12 September 2026: assess_payram_project, check_node_sync, check_payment_readiness, create_payment_link, explain_payment_flow, explain_payram_basics, explain_payram_concepts, explain_referral_flow, and 44 more.
It answered our last check on 20 October 2026 in 334 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.payram.com/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.payram. Endpoint host: mcp.payram.com. ARD identifier: urn:air:io.github.payram:mcp:payram-helper-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.