# com.payram/mcp Install, configure, operate and integrate self-hosted PayRam crypto payment gateways. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.2.0 - **Author:** com.payram - **License:** Unknown - **Endpoints:** streamable-http https://mcp.payram.com/mcp - **Source:** https://github.com/PayRam/payram-mcp - **Endpoint health:** reachable (last checked 2026-10-08T19:54:59.251Z, 1 sample) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-10-08T19:54:43.912Z - **Version scanned:** HEAD - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. ## Tools 40 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `get_payram_doc_by_id` — Returns the markdown for a Payram doc given its id, e.g. "features/payouts". - `list_payram_docs` — Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as "features". - `explain_payram_basics` — Explain Payram's product pillars, architecture, payments, and payouts capabilities. - `get_payram_links` — Surface official documentation, website, and community links. - `explain_payment_flow` — Describe how payments move from customer initiation through settlement. - `explain_payram_concepts` — Glossary-backed explanation of Payram terminology and constraints. - `explain_referrals_basics` — Summarize how Payram referral campaigns are configured and managed. - `explain_referral_flow` — Detail the referrer/referee lifecycle and required APIs. - `get_referral_dashboard_guide` — Explain how to embed and manage the referral dashboard experience. - `prepare_payram_test` — Confirm hosting, credentials, and environment variables before generating demo apps. - `check_node_sync` — Per-chain node health verdict: healthy / lagging / unreachable / listener-down. - `check_payment_readiness` — Diagnoses what is NOT yet set up to accept payments, per blockchain: missing deposit wallet, - `create_payment_link` — Creates a PayRam checkout (payment) link and returns the hosted URL plus a reference_id. - `get_daily_volume` — Returns the total payment volume for a given date, with breakdowns by network and currency. - `get_payment_summary` — Returns payment counts: total, open, closed, and cancelled. - `get_unswept_balances` — Returns unswept (unsettled) balances across all wallets, broken down by blockchain and currency. - `list_currencies` — Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). - `list_platforms` — Lists all external platforms (projects) for the authenticated user. - `list_recipients` — Lists saved withdrawal recipients (payout beneficiaries). - `lookup_payment` — Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID. - `restart_payram_worker` — REMEDIATION ACTION (write): restarts a blockchain listener worker via supervisor — the - `search_payments` — Search and filter payments with full control over status, network, currency, dates, - `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` - `payram_runbook` - `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 - `assess_payram_project` — Inspects dependency files, frameworks, and .env status to suggest the next integration actions. - `snippet_nextjs_payment_route` — Returns a Next.js App Router API route that calls Payram's create-payment HTTP API. - `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_laravel_payment_route` — Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint. - `snippet_go_payment_handler` — Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API. - `snippet_spring_payment_controller` — Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint. - `generate_payment_sdk_snippet` — Generates backend code using the official Payram JS/TS SDK to create a payment. - `generate_payment_http_snippet` — Generates a raw HTTP sample for creating a Payram payment in the requested language. - `generate_payment_status_snippet` — Generates backend code to query the status of a Payram payment. - `generate_payment_route_snippet` — Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment. - `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_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 ## Install **Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. **Cautions** (coverage gaps and advisories — never blocking) - No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it. - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"mcp\": {\n \"type\": \"http\",\n \"url\": \"https://mcp.payram.com/mcp\"\n }\n }\n}" ``` ## Blast radius Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface. - Floor 9, ceiling 27 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/com.payram%2Fmcp - Install plan: https://forgeregistry.com/api/v1/packages/com.payram%2Fmcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/com.payram%2Fmcp - HTML page: https://forgeregistry.com/registry/com.payram%2Fmcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.