# PayRam

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

- name: com.payram/mcp
- version: 1.2.0
- connection class: R0 (autonomous)
- trust: 100/100
- quality: 84/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.payram%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/com.payram%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 99
- freshness: 100
- provenance: 100
- drivers: +repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-98% +updated-13d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 84/100 (good)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 300000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 44 of 44 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 6,320 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 67 tool changes in 30 days
- fail `stability.rug_pull`: 5 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 44, about 6,320 tokens to load them all
- tool set hash: fda52b3d09c14bf054cdd5d4a2c4e1e7
- tools last changed: 2026-10-11T19:37:28.283Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.payram/mcp.svg)](https://protogrid.dev/servers/com.payram/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-11 `explain_payram_security` added
  - 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.
- 2026-10-11 `onboard_agent_setup` changed (title, description, annotations) **meaning changed**
  - before: Quick start for an agent installing PayRam on a VPS: returns the default headless plan (testnet, USDC on Base) with exact commands and the human hand-offs. Same as payram_setup_plan with defaults; call that tool to personalise (domain, mainnet, BTC, operator, Shopify/WooCommerce).
  - after: Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).
- 2026-10-11 `test_payram_connection` changed (title, description, annotations)
  - before: 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. For a full diagnosis use payram_doctor.
  - after: 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.
- 2026-10-11 `list_payram_docs` changed (description)
  - before: Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as "features".
  - after: Lists the available Payram doc ids. Optionally scope by a prefix such as "features".
- 2026-10-11 `generate_mock_webhook_event` changed (outputSchema)
- 2026-10-11 `generate_webhook_event_router` changed (outputSchema)
- 2026-10-11 `generate_webhook_handler` changed (outputSchema)
- 2026-10-11 `get_agent_setup_flow` changed (description)
  - before: Returns the canonical PayRam headless-agent guide (payram-scripts PAYRAM_HEADLESS_AGENT.md): 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.
  - after: 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.
- 2026-10-11 `payram_runbook` changed (description, inputSchema, outputSchema)
  - before: 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. Omit task to list them.
  - after: 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.
- 2026-10-11 `payram_troubleshoot` added
  - 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.

Full history: https://api.protogrid.dev/v1/servers/com.payram%2Fmcp/changes

## Remotes

- https://mcp.payram.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.9811321)

## Packages

_none_

## 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 it does not), and how to verify the report.
- `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 beneficiaries; use generate_payout_sdk_snippet for one-off direct payouts.
- `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 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.)
- `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 (~11k tokens). For a short personalised plan use payram_setup_plan.
- `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 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.
- `payram_ops_playbook`: Exact, copy-paste recipes for day-2 operations and troubleshooting that YOU run against the merchant's PayRam API with credentials that stay on your machine: which endpoint, which credential (public / dashboard JWT / project API key), a curl+jq command, how to read the answer, and what not to do. Start with "connect". Tasks: connect, health, version_check, workers, restart_worker, node_sync, site_url, payment_options, unswept_funds, payments_today, payment_lookup, stuck_payment, create_payment_link, payouts, webhooks, logs, daily_check. Omit task to list them.
- `payram_runbook`: Step-by-step procedures for changes to a running PayRam, each step marked agent vs human with hard stops: set_site_url, change_domain, ssl_setup, ssl_renewal_fix, firewall_ports, upgrade, backup, restore, add_chain, smart_bridge, mainnet_cutover, operator_setup, rotate_api_key, reset_test_install, shopify_connector, woocommerce_plugin, secure_analytics_mcp, install_failed, custom_port_or_proxy, external_database, forgot_root_password. Omit task to list them.
- `payram_setup_plan`: Start here to install PayRam on a VPS. Returns an ordered, personalised plan — prepare server → install → claim admin + set public URL → wallets (incl. Smart Bridge review) → API key + first payment link → hardening → store/app integration — with who runs each step (agent shell vs human/dashboard), exact commands, what success looks like, and hard stops that need the human (cold wallet, mainnet 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.
- `payram_troubleshoot`: Something is not working? Describe the problem in plain words and/or paste the error or log text. Returns the known PayRam problems it matches, what each usually means, how to confirm it and the fix, plus which tool to use next. Needs no credentials and no access to the server; what you paste is not stored. Call with nothing to list known problems. For a live check of a running server use payram_doctor.
- `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 key is accepted. Never creates payments.