Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
PayRam Helper is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
44
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Remote MCP server to integrate and validate self-hosted PayRam deployments.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http payram-helper-mcp https://mcp.payram.com/
# 2 — ask your agent for something these tools do
# payram_setup_plan, payram_doctor, payram_troubleshoot and 41 more
PayRam Helper costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PAAll 2 servers
PayRam2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http payram-helper-mcp https://mcp.payram.com/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
44 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 sp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | agent = headless CLI after a one-time interactive install; human = installer + web dashboard |
| network | string | no | testnet = free test coins (recommended first); mainnet = real money |
| domain | string | no | Public hostname for the gateway, e.g. pay.example.com. Omit if you only have an IP for now. |
| ssl | string | no | letsencrypt (needs domain), own_certificate, proxy (Cloudflare/your own reverse proxy terminates TLS), none. Default: letsencrypt with a domain, none without. |
| role | string | no | 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 |
| wallet | string | no | First deposit wallet: usdc_base (smart-contract wallet on Base, needs a little gas), btc (xpub, no gas), or both |
| stage | string | no | Where you are now; the plan starts from the next step |
| access | string | no | 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. |
| integration | string | no | What will take payments once the gateway is up |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseUrl | string | no | 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 hoste |
| apiKey | string | no | Optional project API key to validate (never creates anything). Passing it puts the key in this conversation; prefer running payram_ops_playbook "connect" locally. |
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_d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symptom | string | no | The problem in plain words, e.g. "payment link opens localhost" or "502 after upgrade". |
| output | string | no | Error text or log lines to match. Remove API keys, tokens, passwords and seed phrases first. |
| area | string | no | Narrow the search to one area. |
| id | string | no | Show one known problem by its id (from an earlier answer). |
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, ex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | no | Which runbook. Omit to list all. |
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | no | Which recipe. Omit to get the index of tasks. |
Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.
No parameter schema on file.
Returns a step-by-step checklist of everything a merchant must configure to start using Payram.
No parameter schema on file.
Suggests a recommended backend folder/file structure for integrating Payram.
No parameter schema on file.
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.
No parameter schema on file.
Generates backend code using the official Payram JS/TS SDK to create a payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | Target framework for the SDK payment snippet. generic-http provides a framework-agnostic example. |
Generates a raw HTTP sample for creating a Payram payment in the requested language.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | yes | Programming language for the HTTP payment creation snippet |
Generates backend code to query the status of a Payram payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| style | string | yes | Style of code snippet: sdk uses the Payram SDK, http uses raw HTTP requests |
Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | Web framework for the payment route handler (Express.js or Next.js) |
Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.
No parameter schema on file.
Returns an Express router that posts to Payram's /api/v1/payment endpoint.
No parameter schema on file.
Returns a FastAPI handler that calls Payram's create-payment HTTP API.
No parameter schema on file.
Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.
No parameter schema on file.
Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.
No parameter schema on file.
Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.
No parameter schema on file.
Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | Target framework for the payout SDK snippet |
Generates backend code to query the status of a payout using the Payram SDK.
No parameter schema on file.
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.
No parameter schema on file.
Generates a backend route or service snippet to create a referral event using the Payram SDK.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | Target framework for the referral SDK snippet |
Generates a snippet to validate referral IDs, statuses, and eligibility.
No parameter schema on file.
Generates code to fetch referral progress, rewards, or status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| style | string | yes | Style of code snippet: sdk uses the Payram SDK, backend-only shows direct API calls |
Generates a backend route such as /api/referrals/create for logging referral events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | Web framework for the referral route handler (Express.js or Next.js) |
Generates backend code to handle Payram webhook HTTP requests.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | yes | Web framework for the webhook handler code |
Generates a backend event router that dispatches Payram webhook events to domain handlers.
No parameter schema on file.
Generates a snippet to send mock Payram webhook events to your local endpoint for testing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
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? Us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part | string | no | Which piece to emit: 'schema' (ledger DDL), 'webhook' (cumulative-credit handler), 'settle' (atomic invoice debit), or 'all'. |
| framework | string | no | Server framework for the webhook handler + settle function. |
Explain Payram's product pillars, architecture, payments, and payouts capabilities.
No parameter schema on file.
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.
No parameter schema on file.
Surface official documentation, website, and community links.
No parameter schema on file.
Describe how payments move from customer initiation through settlement.
No parameter schema on file.
Glossary-backed explanation of Payram terminology and constraints.
No parameter schema on file.
Summarize how Payram referral campaigns are configured and managed.
No parameter schema on file.
Detail the referrer/referee lifecycle and required APIs.
No parameter schema on file.
Explain how to embed and manage the referral dashboard experience.
No parameter schema on file.
Confirm hosting, credentials, and environment variables before generating demo apps.
No parameter schema on file.
Returns the markdown for a Payram doc given its id, e.g. "features/payouts".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
Lists the available Payram doc ids. Optionally scope by a prefix such as "features".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prefix | string | no | — |
Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | yes | Programming language for the application (node for JavaScript/TypeScript) |
| framework | string | yes | Web framework to use for scaffolding the application |
| appName | string | no | Name for the generated application. If not provided, defaults to payram-{framework}-starter |
| includeWebhooks | boolean | no | Whether to include webhook handler code in the scaffolded application |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseUrl | string | no | PayRam URL, same origin as the dashboard (e.g. https://pay.example.com). Defaults to PAYRAM_BASE_URL in local mode. |
| apiKey | string | no | Optional project API key to validate (nothing is created). Passing it exposes the key in this conversation. |
Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install PayRam Helper or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish PayRam Helper can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.