# PayRam (remote · mcp.payram.com)

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

- Trust score: 89/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `mcp.payram.com`: 89/100 (this document), [markdown](https://verifymcp.io/servers/com-payram-mcp/mcp.md), [page](https://verifymcp.io/servers/com-payram-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.payram.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3997 tokens (~47/item across 84 items; 44 tools + 40 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 44 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 46 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-payram-mcp": {
      "type": "http",
      "url": "https://mcp.payram.com/mcp"
    }
  }
}
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-payram-mcp": {
      "type": "remote",
      "url": "https://mcp.payram.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-payram-mcp --url 'https://mcp.payram.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-payram-mcp:
    url: "https://mcp.payram.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-payram-mcp": {
      "Transport": "http",
      "Url": "https://mcp.payram.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-payram-mcp -t streamable-http -u 'https://mcp.payram.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-payram-mcp": {
      "type": "http",
      "url": "https://mcp.payram.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-09 (score 89, +1)

- [security] Stability: 0.97 → pass

### 2026-11-07 (score 88, +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.

### 2026-11-06 (score 87, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 87, +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.

### 2026-11-03 (score 86, +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.

### 2026-11-01 (score 85, +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.

### 2026-10-30 (score 84, +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.

### 2026-10-27 (score 83, +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.

## MCP tools (44)

### `payram_setup_plan` (~447 tokens)

Plan a PayRam install (step by step)

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.

Input parameters:

- `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

Output parameters:

- `humanDecisions` (array)
- `inputs` (object)
- `nextTools` (array)
- `phases` (array)
- `summary` (string)
- `warnings` (array)

### `payram_doctor` (~177 tokens)

Diagnose a PayRam server

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.

Input parameters:

- `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…

Output parameters:

- `baseUrl` (string|null)
- `failedStage` (string|null): First failing stage, null when healthy
- `findings` (array)
- `healthy` (boolean)
- `latestVersion` (string|null)
- `likelyCauses` (array): Ranked causes for the first failing stage
- `nextCall`: The single most useful tool call to make next
- `nextSteps` (array)
- `setupStage`: Pass as payram_setup_plan stage once the server answers PayRam health; null when not reachable
- `version` (string|null)
- `warnings` (array)

### `payram_troubleshoot` (~184 tokens)

Troubleshoot a PayRam problem

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.

Input parameters:

- `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".

Output parameters:

- `gather` (array)
- `index` (array)
- `matches` (array)
- `warning` (string)

### `payram_runbook` (~131 tokens)

PayRam runbooks (one-off admin tasks)

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.

Input parameters:

- `task` (string): Which runbook. Omit to list all.

Output parameters:

- `runbook` (object)
- `tasks` (array)

### `payram_ops_playbook` (~157 tokens)

PayRam ops playbook (direct API recipes)

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.

Input parameters:

- `task` (string): Which recipe. Omit to get the index of tasks.

Output parameters:

- `recipe` (object)
- `tasks` (array)

### `generate_env_template` (~30 tokens)

Generate Payram .env Template

Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.

Output parameters:

- `description` (string)
- `envExample` (string)
- `notes` (string)
- `title` (string)
- `variables` (array)

### `generate_setup_checklist` (~28 tokens)

Generate Payram Setup Checklist

Returns a step-by-step checklist of everything a merchant must configure to start using Payram.

Output parameters:

- `description` (string)
- `items` (array)
- `notes` (string)
- `title` (string)

### `suggest_file_structure` (~22 tokens)

Suggest Payram File Structure

Suggests a recommended backend folder/file structure for integrating Payram.

Output parameters:

- `description` (string)
- `notes` (string)
- `root`
- `title` (string)

### `get_agent_setup_flow` (~57 tokens)

Get the headless agent guide (full reference)

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.

Output parameters:

- `description` (string)
- `markdown` (string)
- `title` (string)

### `generate_payment_sdk_snippet` (~52 tokens)

Generate SDK payment snippet

Generates backend code using the official Payram JS/TS SDK to create a payment.

Input parameters:

- `framework` (string, required): Target framework for the SDK payment snippet. generic-http provides a framework-agnostic example.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_payment_http_snippet` (~42 tokens)

Generate HTTP payment snippet

Generates a raw HTTP sample for creating a Payram payment in the requested language.

Input parameters:

- `language` (string, required): Programming language for the HTTP payment creation snippet

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_payment_status_snippet` (~48 tokens)

Generate payment status snippet

Generates backend code to query the status of a Payram payment.

Input parameters:

- `style` (string, required): Style of code snippet: sdk uses the Payram SDK, http uses raw HTTP requests

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_payment_route_snippet` (~54 tokens)

Generate payment route snippet

Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.

Input parameters:

- `framework` (string, required): Web framework for the payment route handler (Express.js or Next.js)

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `snippet_nextjs_payment_route` (~29 tokens)

Next.js create-payment route snippet

Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `snippet_express_payment_route` (~28 tokens)

Express create-payment route snippet

Returns an Express router that posts to Payram's /api/v1/payment endpoint.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `snippet_fastapi_payment_route` (~26 tokens)

FastAPI create-payment route snippet

Returns a FastAPI handler that calls Payram's create-payment HTTP API.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `snippet_laravel_payment_route` (~29 tokens)

Laravel create-payment route snippet

Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `snippet_go_payment_handler` (~28 tokens)

Go (Gin) create-payment route snippet

Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `snippet_spring_payment_controller` (~28 tokens)

Spring Boot create-payment controller snippet

Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_payout_sdk_snippet` (~44 tokens)

Generate payout SDK snippet

Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.

Input parameters:

- `framework` (string, required): Target framework for the payout SDK snippet

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_payout_status_snippet` (~28 tokens)

Generate payout status SDK snippet

Generates backend code to query the status of a payout using the Payram SDK.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_payout_recipient_flow_snippet` (~55 tokens)

Generate 3-step recipient payout 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.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_referral_sdk_snippet` (~44 tokens)

Generate referral SDK snippet

Generates a backend route or service snippet to create a referral event using the Payram SDK.

Input parameters:

- `framework` (string, required): Target framework for the referral SDK snippet

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_referral_validation_snippet` (~25 tokens)

Generate referral validation snippet

Generates a snippet to validate referral IDs, statuses, and eligibility.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_referral_status_snippet` (~49 tokens)

Generate referral status snippet

Generates code to fetch referral progress, rewards, or status.

Input parameters:

- `style` (string, required): Style of code snippet: sdk uses the Payram SDK, backend-only shows direct API calls

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_referral_route_snippet` (~48 tokens)

Generate referral route snippet

Generates a backend route such as /api/referrals/create for logging referral events.

Input parameters:

- `framework` (string, required): Web framework for the referral route handler (Express.js or Next.js)

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_webhook_handler` (~35 tokens)

Generate Payram webhook HTTP handler

Generates backend code to handle Payram webhook HTTP requests.

Input parameters:

- `framework` (string, required): Web framework for the webhook handler code

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_webhook_event_router` (~27 tokens)

Generate Payram webhook event router

Generates a backend event router that dispatches Payram webhook events to domain handlers.

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_mock_webhook_event` (~64 tokens)

Generate mock Payram webhook event

Generates a snippet to send mock Payram webhook events to your local endpoint for testing.

Input parameters:

- `language` (string, required): Language/tool for the mock webhook request (curl for command-line testing)
- `status` (string, required): Payment status to simulate in the mock webhook event

Output parameters:

- `meta` (object)
- `notes` (string)
- `snippet` (string)
- `title` (string)

### `generate_topup_integration_snippet` (~157 tokens)

Generate top-up wallet integration

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.)

Input parameters:

- `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'.

Output parameters:

- `notes` (string)
- `snippet` (string)
- `title` (string)

### `explain_payram_basics` (~26 tokens)

Payram Basics Overview

Explain Payram's product pillars, architecture, payments, and payouts capabilities.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `explain_payram_security` (~54 tokens)

Is PayRam safe? Security and trust

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.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `get_payram_links` (~20 tokens)

Payram Important Links

Surface official documentation, website, and community links.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `explain_payment_flow` (~19 tokens)

Payment Flow Guide

Describe how payments move from customer initiation through settlement.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `explain_payram_concepts` (~22 tokens)

Core Payram Concepts

Glossary-backed explanation of Payram terminology and constraints.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `explain_referrals_basics` (~24 tokens)

Referral Basics Overview

Summarize how Payram referral campaigns are configured and managed.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `explain_referral_flow` (~21 tokens)

Referral Flow Guide

Detail the referrer/referee lifecycle and required APIs.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `get_referral_dashboard_guide` (~23 tokens)

Referral Dashboard Guide

Explain how to embed and manage the referral dashboard experience.

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `prepare_payram_test` (~23 tokens)

Payram Test Readiness Checklist

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

Output parameters:

- `description` (string)
- `notes` (string)
- `sections` (array)
- `title` (string)

### `get_payram_doc_by_id` (~40 tokens)

Get Payram Doc By ID

Returns the markdown for a Payram doc given its id, e.g. "features/payouts".

Input parameters:

- `id` (string, required)

Output parameters:

- `id` (string)
- `markdown` (string)
- `path` (string)
- `url` (string)

### `list_payram_docs` (~36 tokens)

List Payram Docs

Lists the available Payram doc ids. Optionally scope by a prefix such as "features".

Input parameters:

- `prefix` (string)

Output parameters:

- `count` (number)
- `docs` (array)
- `prefix` (string)

### `scaffold_payram_app` (~119 tokens)

Scaffold Payram Payments & Payouts App

Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.

Input parameters:

- `appName` (string): Name for the generated application. If not provided, defaults to payram-{framework}-starter
- `framework` (string, required): Web framework to use for scaffolding the application
- `includeWebhooks` (boolean): Whether to include webhook handler code in the scaffolded application
- `language` (string, required): Programming language for the application (node for JavaScript/TypeScript)

Output parameters:

- `appName` (string)
- `files` (array)
- `framework` (string)
- `instructions` (string)
- `language` (string)

### `test_payram_connection` (~118 tokens)

Test PayRam connectivity (deprecated)

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.

Input parameters:

- `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.

Output parameters:

- `baseUrl` (string)
- `errorMessage` (string)
- `keyChecked` (boolean)
- `ok` (boolean)
- `payramVersion` (string)

### `onboard_agent_setup` (~41 tokens)

Onboard: install PayRam as an agent (deprecated)

Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).

Output parameters:

- `description` (string)
- `markdown` (string)
- `title` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-payram-mcp/mcp#diagnostics

## Score history

- 2026-11-22: 89
- 2026-11-21: 89
- 2026-11-20: 89
- 2026-11-19: 89
- 2026-11-18: 89
- 2026-11-17: 89
- 2026-11-16: 89
- 2026-11-15: 89
- 2026-11-14: 89
- 2026-11-13: 89
- 2026-11-12: 89
- 2026-11-11: 89
- 2026-11-10: 89
- 2026-11-09: 89
- 2026-11-08: 88
- 2026-11-07: 88
- 2026-11-06: 87
- 2026-11-05: 87
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 84
- 2026-10-30: 84
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 82
- 2026-10-25: 82
- 2026-10-24: 81

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.payram.com/mcp
- Repository: https://github.com/PayRam/payram-mcp
- Website: https://mcp.payram.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-payram-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-payram-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-payram-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-payram-mcp/mcp
