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 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.
22
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http payram-mcp https://mcp.payram.com/mcp
# 2 — ask your agent for something these tools do
# prepare_payram_test, assess_payram_project, generate_payment_sdk_snippet and 19 more
PayRam 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-mcp https://mcp.payram.com/mcpReconnect, 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
22 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.
Confirm hosting, credentials, and environment variables before generating demo apps.
No parameter schema on file.
Inspects dependency files, frameworks, and .env status to suggest the next integration actions.
No parameter schema on file.
Generates backend code using the official Payram JS/TS SDK to create a payment.
No parameter schema on file.
Generates a raw HTTP sample for creating a Payram payment in the requested language.
No parameter schema on file.
Generates backend code to query the status of a Payram payment.
No parameter schema on file.
Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.
No parameter schema on file.
Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.
No parameter schema on file.
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.
No parameter schema on file.
Generates a snippet to validate referral IDs, statuses, and eligibility.
No parameter schema on file.
Generates code to fetch referral progress, rewards, or status.
No parameter schema on file.
Generates a backend route such as /api/referrals/create for logging referral events.
No parameter schema on file.
Generates backend code to handle Payram webhook HTTP requests.
No parameter schema on file.
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.
No parameter schema on file.
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 (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.
No parameter schema on file.
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).
No parameter schema on file.
Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
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 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.2.0.
1.2.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 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.