PayRam
REMOTE · MCP.PAYRAM.COM
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
Available components
Last scanned (18 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3997 tokens (~47/item across 84 items; 44 tools + 40 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 44 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 46 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Probed https://mcp.payram.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.payram.com | CN=YR2,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 655fe7114f79d990aa95bfc72fb1fec6f08 |
| SANs: mcp.payram.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.payram.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| payram.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.payram.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.payram.com/mcp | HTTPS enforced | 308 | https://mcp.payram.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_payment_flow Payment Flow Guide ~19
Describe how payments move from customer initiation through settlement.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
explain_payram_basics Payram Basics Overview ~26
Explain Payram's product pillars, architecture, payments, and payouts capabilities.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
explain_payram_concepts Core Payram Concepts ~22
Glossary-backed explanation of Payram terminology and constraints.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
explain_payram_security Is PayRam safe? Security and trust ~54
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
explain_referral_flow Referral Flow Guide ~21
Detail the referrer/referee lifecycle and required APIs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
explain_referrals_basics Referral Basics Overview ~24
Summarize how Payram referral campaigns are configured and managed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
generate_env_template Generate Payram .env Template ~30
Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| envExample | string | yes | – |
| notes | string | – | – |
| title | string | yes | – |
| variables | array | yes | – |
No examples provided.
generate_mock_webhook_event Generate mock Payram webhook event ~64
Generates a snippet to send mock Payram webhook events to your local endpoint for testing.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | Language/tool for the mock webhook request (curl for command-line testing) |
| status | string | yes | Payment status to simulate in the mock webhook event |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payment_http_snippet Generate HTTP payment snippet ~42
Generates a raw HTTP sample for creating a Payram payment in the requested language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | Programming language for the HTTP payment creation snippet |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payment_route_snippet Generate payment route snippet ~54
Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Web framework for the payment route handler (Express.js or Next.js) |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payment_sdk_snippet Generate SDK payment snippet ~52
Generates backend code using the official Payram JS/TS SDK to create a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework for the SDK payment snippet. generic-http provides a framework-agnostic example. |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payment_status_snippet Generate payment status snippet ~48
Generates backend code to query the status of a Payram payment.
| Name | Type | Req | Description |
|---|---|---|---|
| style | string | yes | Style of code snippet: sdk uses the Payram SDK, http uses raw HTTP requests |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payout_recipient_flow_snippet Generate 3-step recipient payout flow snippet ~55
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payout_sdk_snippet Generate payout SDK snippet ~44
Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework for the payout SDK snippet |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_payout_status_snippet Generate payout status SDK snippet ~28
Generates backend code to query the status of a payout using the Payram SDK.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_referral_route_snippet Generate referral route snippet ~48
Generates a backend route such as /api/referrals/create for logging referral events.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Web framework for the referral route handler (Express.js or Next.js) |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_referral_sdk_snippet Generate referral SDK snippet ~44
Generates a backend route or service snippet to create a referral event using the Payram SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework for the referral SDK snippet |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_referral_status_snippet Generate referral status snippet ~49
Generates code to fetch referral progress, rewards, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| style | string | yes | Style of code snippet: sdk uses the Payram SDK, backend-only shows direct API calls |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_referral_validation_snippet Generate referral validation snippet ~25
Generates a snippet to validate referral IDs, statuses, and eligibility.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_setup_checklist Generate Payram Setup Checklist ~28
Returns a step-by-step checklist of everything a merchant must configure to start using Payram.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| items | array | yes | – |
| notes | string | – | – |
| title | string | yes | – |
No examples provided.
generate_topup_integration_snippet Generate top-up wallet integration ~157
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.)
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Server framework for the webhook handler + settle function. |
| part | string | – | Which piece to emit: 'schema' (ledger DDL), 'webhook' (cumulative-credit handler), 'settle' (atomic invoice debit), or 'all'. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | yes | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_webhook_event_router Generate Payram webhook event router ~27
Generates a backend event router that dispatches Payram webhook events to domain handlers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
generate_webhook_handler Generate Payram webhook HTTP handler ~35
Generates backend code to handle Payram webhook HTTP requests.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Web framework for the webhook handler code |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
get_agent_setup_flow Get the headless agent guide (full reference) ~57
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| markdown | string | yes | – |
| title | string | yes | – |
No examples provided.
get_payram_doc_by_id Get Payram Doc By ID ~40
Returns the markdown for a Payram doc given its id, e.g. "features/payouts".
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| markdown | string | yes | – |
| path | string | yes | – |
| url | string | – | – |
No examples provided.
get_payram_links Payram Important Links ~20
Surface official documentation, website, and community links.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
get_referral_dashboard_guide Referral Dashboard Guide ~23
Explain how to embed and manage the referral dashboard experience.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
list_payram_docs List Payram Docs ~36
Lists the available Payram doc ids. Optionally scope by a prefix such as "features".
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| docs | array | yes | – |
| prefix | string | – | – |
No examples provided.
onboard_agent_setup Onboard: install PayRam as an agent (deprecated) ~41
Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| markdown | string | yes | – |
| title | string | yes | – |
No examples provided.
payram_doctor Diagnose a PayRam server ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Optional project API key to validate (never creates anything). Passing it puts the key in this conversation; prefer running payram_ops_playbook "connect" locally. |
| baseUrl | string | – | Public address of the PayRam server, same origin as the dashboard: https://pay.example.com, or just pay.example.com or an IP (https is tried first, then http). No :8080, no path. Required on the host… |
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string|null | yes | – |
| failedStage | string|null | yes | First failing stage, null when healthy |
| findings | array | yes | – |
| healthy | boolean | yes | – |
| latestVersion | string|null | yes | – |
| likelyCauses | array | yes | Ranked causes for the first failing stage |
| nextCall | – | yes | The single most useful tool call to make next |
| nextSteps | array | yes | – |
| setupStage | – | yes | Pass as payram_setup_plan stage once the server answers PayRam health; null when not reachable |
| version | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
payram_ops_playbook PayRam ops playbook (direct API recipes) ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | – | Which recipe. Omit to get the index of tasks. |
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | object | – | – |
| tasks | array | yes | – |
No examples provided.
payram_runbook PayRam runbooks (one-off admin tasks) ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | – | Which runbook. Omit to list all. |
| Name | Type | Req | Description |
|---|---|---|---|
| runbook | object | – | – |
| tasks | array | yes | – |
No examples provided.
payram_setup_plan Plan a PayRam install (step by step) ~447
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | ssh = you can run commands on the server yourself. human_runs_commands = you only chat: the human runs each command and pastes the output back. Ask the user which applies before planning. |
| domain | string | – | Public hostname for the gateway, e.g. pay.example.com. Omit if you only have an IP for now. |
| integration | string | – | What will take payments once the gateway is up |
| network | string | – | testnet = free test coins (recommended first); mainnet = real money |
| path | string | – | agent = headless CLI after a one-time interactive install; human = installer + web dashboard |
| role | string | – | merchant: Take payments for your own business (default). operator: Run PayRam as a platform for other merchants and earn a fee on their volume. Must be chosen before the first project; the role locks… |
| ssl | string | – | letsencrypt (needs domain), own_certificate, proxy (Cloudflare/your own reverse proxy terminates TLS), none. Default: letsencrypt with a domain, none without. |
| stage | string | – | Where you are now; the plan starts from the next step |
| wallet | string | – | First deposit wallet: usdc_base (smart-contract wallet on Base, needs a little gas), btc (xpub, no gas), or both |
| Name | Type | Req | Description |
|---|---|---|---|
| humanDecisions | array | yes | – |
| inputs | object | yes | – |
| nextTools | array | yes | – |
| phases | array | yes | – |
| summary | string | yes | – |
| warnings | array | yes | – |
No examples provided.
payram_troubleshoot Troubleshoot a PayRam problem ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Narrow the search to one area. |
| id | string | – | Show one known problem by its id (from an earlier answer). |
| output | string | – | Error text or log lines to match. Remove API keys, tokens, passwords and seed phrases first. |
| symptom | string | – | The problem in plain words, e.g. "payment link opens localhost" or "502 after upgrade". |
| Name | Type | Req | Description |
|---|---|---|---|
| gather | array | – | – |
| index | array | – | – |
| matches | array | yes | – |
| warning | string | – | – |
No examples provided.
prepare_payram_test Payram Test Readiness Checklist ~23
Confirm hosting, credentials, and environment variables before generating demo apps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| sections | array | yes | – |
| title | string | yes | – |
No examples provided.
scaffold_payram_app Scaffold Payram Payments & Payouts App ~119
Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | – | Name for the generated application. If not provided, defaults to payram-{framework}-starter |
| framework | string | yes | Web framework to use for scaffolding the application |
| includeWebhooks | boolean | – | Whether to include webhook handler code in the scaffolded application |
| language | string | yes | Programming language for the application (node for JavaScript/TypeScript) |
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | yes | – |
| files | array | yes | – |
| framework | string | yes | – |
| instructions | string | yes | – |
| language | string | yes | – |
No examples provided.
snippet_express_payment_route Express create-payment route snippet ~28
Returns an Express router that posts to Payram's /api/v1/payment endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
snippet_fastapi_payment_route FastAPI create-payment route snippet ~26
Returns a FastAPI handler that calls Payram's create-payment HTTP API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
snippet_go_payment_handler Go (Gin) create-payment route snippet ~28
Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
snippet_laravel_payment_route Laravel create-payment route snippet ~29
Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
snippet_nextjs_payment_route Next.js create-payment route snippet ~29
Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
snippet_spring_payment_controller Spring Boot create-payment controller snippet ~28
Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | – |
| notes | string | – | – |
| snippet | string | yes | – |
| title | string | yes | – |
No examples provided.
suggest_file_structure Suggest Payram File Structure ~22
Suggests a recommended backend folder/file structure for integrating Payram.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| root | – | yes | – |
| title | string | yes | – |
No examples provided.
test_payram_connection Test PayRam connectivity (deprecated) ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Optional project API key to validate (nothing is created). Passing it exposes the key in this conversation. |
| baseUrl | string | – | PayRam URL, same origin as the dashboard (e.g. https://pay.example.com). Defaults to PAYRAM_BASE_URL in local mode. |
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | – |
| errorMessage | string | – | – |
| keyChecked | boolean | yes | – |
| ok | boolean | yes | – |
| payramVersion | string | – | – |
No examples provided.
How do I install the PayRam MCP server?
PayRam is a hosted endpoint at https://mcp.payram.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.payram.com
claude mcp add --transport http com-payram-mcp 'https://mcp.payram.com/mcp'
What is the PayRam MCP server?
PayRam is an MCP server listed in the public MCP registry as com.payram/mcp. Install, configure, operate and integrate self-hosted PayRam crypto payment gateways. This page covers its hosted endpoint (https://mcp.payram.com/mcp).
Is the PayRam MCP server safe to use?
PayRam scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PayRam MCP server expose?
PayRam exposes 44 tools: payram_setup_plan, payram_doctor, payram_troubleshoot, payram_runbook, payram_ops_playbook, and 39 more. Their descriptions and schemas cost roughly 2,759 tokens of context every time the server is loaded.
Does the PayRam MCP server require authentication?
No. We connected to PayRam without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayRam MCP server still maintained?
PayRam is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PayRam MCP server?
VerifyMCP ran 13 checks on PayRam, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.