PayRam

com.payram/mcpVersion 1.2.0

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

Status

Responds282 msNov 14, 2026, 14:09 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:09 UTC
Latency: 282 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.payram.com/mcpResponds282 msNov 14, 2026, 14:09 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: payram
Remote MCP server URL: https://mcp.payram.com/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"payram","type":"http","url":"https://mcp.payram.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

44 tools

Tools of PayRam
	Description		Read-only	Idempotent	Open world
`explain_payment_flow`Describe how payments move from customer initiation through settlement.	Describe how payments move from customer initiation through settlement.	No	Yes	Yes	No
`explain_payram_basics`Explain Payram's product pillars, architecture, payments, and payouts capabilities.	Explain Payram's product pillars, architecture, payments, and payouts capabilities.	No	Yes	Yes	No
`explain_payram_concepts`Glossary-backed explanation of Payram terminology and constraints.	Glossary-backed explanation of Payram terminology and constraints.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`explain_referral_flow`Detail the referrer/referee lifecycle and required APIs.	Detail the referrer/referee lifecycle and required APIs.	No	Yes	Yes	No
`explain_referrals_basics`Summarize how Payram referral campaigns are configured and managed.	Summarize how Payram referral campaigns are configured and managed.	No	Yes	Yes	No
`generate_env_template`Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.	Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.	No	Yes	Yes	No
`generate_mock_webhook_event`Generates a snippet to send mock Payram webhook events to your local endpoint for testing.	Generates a snippet to send mock Payram webhook events to your local endpoint for testing.	No	Yes	Yes	No
`generate_payment_http_snippet`Generates a raw HTTP sample for creating a Payram payment in the requested language.	Generates a raw HTTP sample for creating a Payram payment in the requested language.	No	Yes	Yes	No
`generate_payment_route_snippet`Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.	Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.	No	Yes	Yes	No
`generate_payment_sdk_snippet`Generates backend code using the official Payram JS/TS SDK to create a payment.	Generates backend code using the official Payram JS/TS SDK to create a payment.	No	Yes	Yes	No
`generate_payment_status_snippet`Generates backend code to query the status of a Payram payment.	Generates backend code to query the status of a Payram payment.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`generate_payout_sdk_snippet`Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.	Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.	No	Yes	Yes	No
`generate_payout_status_snippet`Generates backend code to query the status of a payout using the Payram SDK.	Generates backend code to query the status of a payout using the Payram SDK.	No	Yes	Yes	No
`generate_referral_route_snippet`Generates a backend route such as /api/referrals/create for logging referral events.	Generates a backend route such as /api/referrals/create for logging referral events.	No	Yes	Yes	No
`generate_referral_sdk_snippet`Generates a backend route or service snippet to create a referral event using the Payram SDK.	Generates a backend route or service snippet to create a referral event using the Payram SDK.	No	Yes	Yes	No
`generate_referral_status_snippet`Generates code to fetch referral progress, rewards, or status.	Generates code to fetch referral progress, rewards, or status.	No	Yes	Yes	No
`generate_referral_validation_snippet`Generates a snippet to validate referral IDs, statuses, and eligibility.	Generates a snippet to validate referral IDs, statuses, and eligibility.	No	Yes	Yes	No
`generate_setup_checklist`Returns a step-by-step checklist of everything a merchant must configure to start using Payram.	Returns a step-by-step checklist of everything a merchant must configure to start using Payram.	No	Yes	Yes	No
`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.)	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.)	No	Yes	Yes	No
`generate_webhook_event_router`Generates a backend event router that dispatches Payram webhook events to domain handlers.	Generates a backend event router that dispatches Payram webhook events to domain handlers.	No	Yes	Yes	No
`generate_webhook_handler`Generates backend code to handle Payram webhook HTTP requests.	Generates backend code to handle Payram webhook HTTP requests.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`get_payram_doc_by_id`Returns the markdown for a Payram doc given its id, e.g. "features/payouts".	Returns the markdown for a Payram doc given its id, e.g. "features/payouts".	No	Yes	Yes	No
`get_payram_links`Surface official documentation, website, and community links.	Surface official documentation, website, and community links.	No	Yes	Yes	No
`get_referral_dashboard_guide`Explain how to embed and manage the referral dashboard experience.	Explain how to embed and manage the referral dashboard experience.	No	Yes	Yes	No
`list_payram_docs`Lists the available Payram doc ids. Optionally scope by a prefix such as "features".	Lists the available Payram doc ids. Optionally scope by a prefix such as "features".	No	Yes	Yes	No
`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).	Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	Yes
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`prepare_payram_test`Confirm hosting, credentials, and environment variables before generating demo apps.	Confirm hosting, credentials, and environment variables before generating demo apps.	No	Yes	Yes	No
`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.	Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.	No	Yes	Yes	No
`snippet_express_payment_route`Returns an Express router that posts to Payram's /api/v1/payment endpoint.	Returns an Express router that posts to Payram's /api/v1/payment endpoint.	No	Yes	Yes	No
`snippet_fastapi_payment_route`Returns a FastAPI handler that calls Payram's create-payment HTTP API.	Returns a FastAPI handler that calls Payram's create-payment HTTP API.	No	Yes	Yes	No
`snippet_go_payment_handler`Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.	Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.	No	Yes	Yes	No
`snippet_laravel_payment_route`Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.	Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.	No	Yes	Yes	No
`snippet_nextjs_payment_route`Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.	Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.	No	Yes	Yes	No
`snippet_spring_payment_controller`Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.	Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.	No	Yes	Yes	No
`suggest_file_structure`Suggests a recommended backend folder/file structure for integrating Payram.	Suggests a recommended backend folder/file structure for integrating Payram.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	Yes

Details

Registry status: Active
Published: Oct 7, 2026
Updated: Oct 7, 2026
Website: https://mcp.payram.com/⁠ (opens in a new tab)
Repository: https://github.com/PayRam/payram-mcp⁠ (opens in a new tab)
Categories (suggested): Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing