PayRam
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
| Endpoint | https://mcp.payram.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.2.0 |
| Now | 44 tools · grade C (65) · pin ts_6a5a4c85d92237bbf217615c58bcff57 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 08:17 UTC / 2026-10-27 08:17 UTC |
| Grade over time | 2026-10-27: C (65), 44 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: payram_setup_plan payram_doctor payram_troubleshoot payram_runbook payram_ops_playbook generate_env_template generate_setup_checklist suggest_file_structure get_agent_setup_flow generate_payment_sdk_snippet generate_payment_http_snippet generate_payment_status_snippet generate_payment_route_snippet snippet_nextjs_payment_route snippet_express_payment_route snippet_fastapi_payment_route snippet_laravel_payment_route snippet_go_payment_handler snippet_spring_payment_controller generate_payout_sdk_snippet generate_payout_status_snippet generate_payout_recipient_flow_snippet generate_referral_sdk_snippet generate_referral_validation_snippet generate_referral_status_snippet generate_referral_route_snippet generate_webhook_handler generate_webhook_event_router generate_mock_webhook_event generate_topup_integration_snippet explain_payram_basics explain_payram_security get_payram_links explain_payment_flow explain_payram_concepts explain_referrals_basics explain_referral_flow get_referral_dashboard_guide prepare_payram_test get_payram_doc_by_id list_payram_docs scaffold_payram_app test_payram_connection onboard_agent_setup
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 sp params: path, network, domain, ssl, role, wallet, stage, access, integration |
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. params: baseUrl, apiKey |
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_d params: symptom, output, area, id |
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, ex params: task |
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_ params: task |
generate_env_template | Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server. params: none |
generate_setup_checklist | Returns a step-by-step checklist of everything a merchant must configure to start using Payram. params: none |
suggest_file_structure | Suggests a recommended backend folder/file structure for integrating Payram. params: none |
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. params: none |
generate_payment_sdk_snippet | Generates backend code using the official Payram JS/TS SDK to create a payment. params: framework* |
generate_payment_http_snippet | Generates a raw HTTP sample for creating a Payram payment in the requested language. params: language* |
generate_payment_status_snippet | Generates backend code to query the status of a Payram payment. params: style* |
generate_payment_route_snippet | Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment. params: framework* |
snippet_nextjs_payment_route | Returns a Next.js App Router API route that calls Payram's create-payment HTTP API. params: none |
snippet_express_payment_route | Returns an Express router that posts to Payram's /api/v1/payment endpoint. params: none |
snippet_fastapi_payment_route | Returns a FastAPI handler that calls Payram's create-payment HTTP API. params: none |
snippet_laravel_payment_route | Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint. params: none |
snippet_go_payment_handler | Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API. params: none |
snippet_spring_payment_controller | Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint. params: none |
generate_payout_sdk_snippet | Generates a backend code snippet for creating a payout using the Payram JS/TS SDK. params: framework* |
generate_payout_status_snippet | Generates backend code to query the status of a payout using the Payram SDK. params: none |
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. params: none |
generate_referral_sdk_snippet | Generates a backend route or service snippet to create a referral event using the Payram SDK. params: framework* |
generate_referral_validation_snippet | Generates a snippet to validate referral IDs, statuses, and eligibility. params: none |
generate_referral_status_snippet | Generates code to fetch referral progress, rewards, or status. params: style* |
generate_referral_route_snippet | Generates a backend route such as /api/referrals/create for logging referral events. params: framework* |
generate_webhook_handler | Generates backend code to handle Payram webhook HTTP requests. params: framework* |
generate_webhook_event_router | Generates a backend event router that dispatches Payram webhook events to domain handlers. params: none |
generate_mock_webhook_event | Generates a snippet to send mock Payram webhook events to your local endpoint for testing. params: language*, status* |
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? Us params: part, framework |
explain_payram_basics | Explain Payram's product pillars, architecture, payments, and payouts capabilities. params: none |
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. params: none |
get_payram_links | Surface official documentation, website, and community links. params: none |
explain_payment_flow | Describe how payments move from customer initiation through settlement. params: none |
explain_payram_concepts | Glossary-backed explanation of Payram terminology and constraints. params: none |
explain_referrals_basics | Summarize how Payram referral campaigns are configured and managed. params: none |
explain_referral_flow | Detail the referrer/referee lifecycle and required APIs. params: none |
get_referral_dashboard_guide | Explain how to embed and manage the referral dashboard experience. params: none |
prepare_payram_test | Confirm hosting, credentials, and environment variables before generating demo apps. params: none |
get_payram_doc_by_id | Returns the markdown for a Payram doc given its id, e.g. "features/payouts". params: id* |
list_payram_docs | Lists the available Payram doc ids. Optionally scope by a prefix such as "features". params: prefix |
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. params: language*, framework*, appName, includeWebhooks |
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. params: baseUrl, apiKey |
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). params: none |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.