# PayRam Helper MCP Server (remote · mcp.payram.com)

Remote MCP server to integrate and validate self-hosted PayRam deployments.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://mcp.payram.com/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 52 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 78/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 3402 tokens (~63/item across 54 items; 52 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

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

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-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

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

### 2026-07-30 (score 68, +1)

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

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

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

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (52)

### `test_payram_connection` (~113 tokens)

Test Payram Connectivity

Checks the /api/v1/payment endpoint on a Payram server using baseUrl and apiKey. If they are not provided, returns a .env template you can add to your workspace.

Input parameters:

- `apiKey` (string): Your Payram API key from the dashboard. If not provided, uses PAYRAM_API_KEY from environment.
- `baseUrl` (string): The base URL of your Payram server (e.g., https://your-server.example). If not provided, uses PAYRAM_BASE_URL from environment.

Output parameters:

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

### `payram_doctor` (~134 tokens)

Diagnose a PayRam setup (one call)

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 when anything PayRam-related fails.

Input parameters:

- `apiKey` (string): Merchant API key (per-project). Defaults to PAYRAM_API_KEY. Obtain headlessly: ./setup_payram_agents.sh ensure-api-key
- `baseUrl` (string): PayRam server base URL. Defaults to PAYRAM_BASE_URL. The installer publishes on port 80 (http://localhost), not :8080.

Output parameters:

- `failedStage`: First failing stage: reachability | api-key | jwt | readiness; null when healthy
- `findings` (array)
- `healthy` (boolean)
- `likelyCauses` (array): Ranked causes for the first failing stage
- `nextSteps` (array)

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

### `assess_payram_project` (~28 tokens)

Assess Payram readiness in an existing codebase

Inspects dependency files, frameworks, and .env status to suggest the next integration actions.

Output parameters:

- `detectedFiles` (array)
- `envStatus` (object)
- `frameworks` (array)
- `packageManagers` (array)
- `payramDependencies` (array)
- `recommendedNextSteps` (array)
- `summary` (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)

### `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` (~44 tokens)

List Payram Docs

Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as "features".

Input parameters:

- `prefix` (string)

Output parameters:

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

### `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` (~75 tokens)

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), faucet URLs, card-to-crypto prerequisites, and status/recovery commands for interrupted sessions.

Output parameters:

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

### `onboard_agent_setup` (~28 tokens)

Get Payram Agent Onboarding Guide

Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction.

Output parameters:

- `description` (string)
- `markdown` (string)
- `title` (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)

### `list_platforms` (~38 tokens)

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.

Output parameters:

- `count` (number)
- `platforms` (array)

### `get_payment_summary` (~50 tokens)

Get Payment Summary

Returns payment counts: total, open, closed, and cancelled. Useful for a quick overview of payment activity.

Input parameters:

- `externalPlatformId` (string): Optional. Auto-discovered from your account if omitted.

Output parameters:

- `cancelledCount` (number)
- `closedCount` (number)
- `openCount` (number)
- `totalCount` (number)

### `lookup_payment` (~94 tokens)

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.

Input parameters:

- `externalPlatformId` (string): Optional. Auto-discovered from your account if omitted.
- `query` (string, required): Search query: transaction hash, email address, reference ID (UUID), customer ID, or invoice ID. The backend auto-detects the query type.

Output parameters:

- `payments` (array)
- `totalCount` (number)

### `search_payments` (~344 tokens)

Search Payments

Search and filter payments with full control over status, network, currency, dates, webhook status, and pagination. Returns a paginated list of matching payments.

Input parameters:

- `createdBy` (array): Filter by creator type.
- `currency` (array): Filter by currency code (e.g. USDC, USDT, BTC, ETH, TRX, CBBTC).
- `dateFrom` (string): Start date filter (ISO 8601, e.g. 2024-01-01T00:00:00Z).
- `dateTo` (string): End date filter (ISO 8601, e.g. 2024-12-31T23:59:59Z).
- `externalPlatformId` (string): Optional. Auto-discovered from your account if omitted.
- `limit` (integer): Number of results per page. Defaults to 50.
- `network` (array): Filter by blockchain network (e.g. BTC, ETH, TRX, BASE, POLYGON).
- `offset` (integer): Pagination offset. Defaults to 0.
- `paymentStatus` (array): Filter by payment status (FILLED = completed).
- `query` (string): Free-text search: tx hash, email, reference ID, customer ID, or invoice ID.
- `sortBy` (string): Sort field. Valid: created_at, updated_at, payment_status, currency, network, block_id, from_address, to_address, invoice_id, reference_id, customer_id, email, created_by.
- `sortDirection` (string): Sort direction. Defaults to DESC.
- `webhookStatus` (array): Filter by webhook delivery status.

Output parameters:

- `limit` (number)
- `offset` (number)
- `payments` (array)
- `showing` (number)
- `totalCount` (number)

### `get_unswept_balances` (~108 tokens)

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. HOT_WALLET_LOW_GAS with the hot-wallet address to fund), pending SCW deployment, or missing cold wallet. Use this to answer "where is my money / why has it not swept".

Output parameters:

- `balances` (array)
- `totalWallets` (number)

### `get_daily_volume` (~83 tokens)

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.

Input parameters:

- `date` (string): Date in YYYY-MM-DD format. Defaults to today (UTC).
- `externalPlatformId` (string): Optional. Auto-discovered from your account if omitted.

Output parameters:

- `byCurrency` (array)
- `byNetwork` (array)
- `date` (string)
- `totalPayments` (number)
- `totalVolumeUSD` (number)

### `list_currencies` (~64 tokens)

List Supported 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 values before creating payments or payouts.

Output parameters:

- `count` (number)
- `currencies` (array)

### `list_recipients` (~55 tokens)

List Payout 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.

Output parameters:

- `count` (number)
- `recipients` (array)

### `create_payment_link` (~146 tokens)

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 on the hosted checkout. Poll status later with lookup_payment (or GET /api/v1/payment/reference/{reference_id}).

Input parameters:

- `amountInUSD` (number, required): Payment amount in USD (must be > 0)
- `customerEmail` (string, required): Customer email (required — the backend validates it as a non-empty email)
- `customerID` (string, required): Your internal customer identifier (sent as customerID, required)

Output parameters:

- `host` (string)
- `reference_id` (string)
- `url` (string)

### `check_node_sync` (~117 tokens)

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 not syncing. Also checks the chain’s listener worker. When something is wrong it names the exact remediation (usually restart_payram_worker). Read-only — run this first; restart second; re-run this ~60s after a restart to confirm recovery.

Output parameters:

- `chains` (array)
- `healthy` (boolean)
- `issues` (array)
- `workers` (array)
- `workersAvailable` (boolean)

### `restart_payram_worker` (~169 tokens)

Restart PayRam Worker

REMEDIATION ACTION (write): restarts a blockchain listener worker via supervisor — the minimal fix when check_node_sync reports a chain as lagging or listener-down. Workflow: run check_node_sync first → restart the named worker → wait ~60s → run check_node_sync again to confirm recovery. A restart does NOT fix an unreachable RPC (fix the RPC config in the dashboard instead). Requires admin JWT with write_system_settings.

Input parameters:

- `all` (boolean): Restart ALL workers. Use only when multiple chains are unhealthy.
- `worker` (string): Worker to restart: a chain code ('BASE', 'ETH', 'BTC', 'TRX', 'POLYGON' → restarts that chain's listener) or a full worker name ('base-listener'). Omit when using all=true.

Output parameters:

- `message` (string)
- `restarted` (string)

### `check_payment_readiness` (~89 tokens)

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 not create wallets itself.

Input parameters:

- `externalPlatformId` (string): Project/platform ID to check currency enablement for (auto-resolved if omitted)

Output parameters:

- `allReady` (boolean)
- `chains` (array)
- `projectId` (string)
- `readyChains` (array)

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 65

## Links

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