# Payram Helper MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.payram%2Fpayram-helper-mcp
Registry id: `mcp-registry/io.github.payram/payram-helper-mcp`
Status: live (checked 2026-10-27T02:42:34.079Z)

## Verdict

Payram Helper MCP server answered 99.85% of Glimind's liveness checks over 30 days, better than 26% of MCP servers, with 454 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (90/100) across 44 tools, costing an agent about 5,892 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.85% | 26% of MCP servers |
| Median handshake latency | 454 ms | 53% of MCP servers |
| p95 handshake latency | 2743 ms | — |
| Checks in 30 days | 4,861 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 26.1 h | — |
| Agent-readiness score | 90/100 (A) | 69% of MCP servers |
| Tools | 44 | — |
| Tool-list size for an agent | ~5,892 tokens | 36% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

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

## Tools (44)

- `explain_payment_flow`: Describe how payments move from customer initiation through settlement.
- `explain_payram_basics`: Explain Payram's product pillars, architecture, payments, and payouts capabilities.
- `explain_payram_concepts`: Glossary-backed explanation of Payram terminology and constraints.
- `explain_payram_security`: Answer "is PayRam safe / trustworthy / audited?": why an agent can use it without holding secrets, the independent smart contract audit (what it covers and what
- `explain_referral_flow`: Detail the referrer/referee lifecycle and required APIs.
- `explain_referrals_basics`: Summarize how Payram referral campaigns are configured and managed.
- `generate_env_template`: Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.
- `generate_mock_webhook_event`: Generates a snippet to send mock Payram webhook events to your local endpoint for testing.
- `generate_payment_http_snippet`: Generates a raw HTTP sample for creating a Payram payment in the requested language.
- `generate_payment_route_snippet`: Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.
- `generate_payment_sdk_snippet`: Generates backend code using the official Payram JS/TS SDK to create a payment.
- `generate_payment_status_snippet`: Generates backend code to query the status of a Payram payment.
- `generate_payout_recipient_flow_snippet`: Generates the recommended OTP-verified payout flow: create recipient → validate OTP → create payout against the saved recipient. Use this for repeat beneficiari
- `generate_payout_sdk_snippet`: Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.
- `generate_payout_status_snippet`: Generates backend code to query the status of a payout using the Payram SDK.
- `generate_referral_route_snippet`: Generates a backend route such as /api/referrals/create for logging referral events.
- `generate_referral_sdk_snippet`: Generates a backend route or service snippet to create a referral event using the Payram SDK.
- `generate_referral_status_snippet`: Generates code to fetch referral progress, rewards, or status.
- `generate_referral_validation_snippet`: Generates a snippet to validate referral IDs, statuses, and eligibility.
- `generate_setup_checklist`: Returns a step-by-step checklist of everything a merchant must configure to start using Payram.
- `generate_topup_integration_snippet`: For EXISTING apps: emits the recommended top-up wallet integration — ledger schema + cumulative-credit webhook handler + atomic invoice-settle function. Credits
- `generate_webhook_event_router`: Generates a backend event router that dispatches Payram webhook events to domain handlers.
- `generate_webhook_handler`: Generates backend code to handle Payram webhook HTTP requests.
- `get_agent_setup_flow`: Returns the canonical PayRam headless-agent guide: agent CLI commands, env vars, merchant vs operator mode, wallet flows, adding chains, troubleshooting. Long (
- `get_payram_doc_by_id`: Returns the markdown for a Payram doc given its id, e.g. "features/payouts".
- `get_payram_links`: Surface official documentation, website, and community links.
- `get_referral_dashboard_guide`: Explain how to embed and manage the referral dashboard experience.
- `list_payram_docs`: Lists the available Payram doc ids. Optionally scope by a prefix such as "features".
- `onboard_agent_setup`: Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).
- `payram_doctor`: Read-only diagnosis of a PayRam server by its public URL — works from the hosted MCP without credentials: reachability, health, TLS certificate, installed vs la
- `payram_ops_playbook`: Exact, copy-paste recipes for day-2 operations and troubleshooting that YOU run against the merchant's PayRam API with credentials that stay on your machine: wh
- `payram_runbook`: Step-by-step procedures for changes to a running PayRam, each step marked agent vs human with hard stops: set_site_url, change_domain, ssl_setup, ssl_renewal_fi
- `payram_setup_plan`: Start here to install PayRam on a VPS. Returns an ordered, personalised plan — prepare server → install → claim admin + set public URL → wallets (incl. Smart Br
- `payram_troubleshoot`: Something is not working? Describe the problem in plain words and/or paste the error or log text. Returns the known PayRam problems it matches, what each usuall
- `prepare_payram_test`: Confirm hosting, credentials, and environment variables before generating demo apps.
- `scaffold_payram_app`: Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
- `snippet_express_payment_route`: Returns an Express router that posts to Payram's /api/v1/payment endpoint.
- `snippet_fastapi_payment_route`: Returns a FastAPI handler that calls Payram's create-payment HTTP API.
- `snippet_go_payment_handler`: Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.
- `snippet_laravel_payment_route`: Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.
- `snippet_nextjs_payment_route`: Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.
- `snippet_spring_payment_controller`: Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.
- `suggest_file_structure`: Suggests a recommended backend folder/file structure for integrating Payram.
- `test_payram_connection`: Deprecated: use payram_doctor, which does this and more. Read-only check that a PayRam server is reachable and healthy and, if an API key is supplied, that the 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.