Home / MCP registry index / com.payram/mcp
PayRam
com.payram/mcp in the official MCP registry.
Endpoint https://mcp.payram.com/mcp. Source: github.com/PayRam/payram-mcp.
The registry describes it as: Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.
We read its 44 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
payram_setup_plan payram_doctor payram_troubleshoot payram_runbook payram_ops_playbook generate_env_template generate_setup_checklist suggest_file_structure get_agent_setup_flow generate_payment_sdk_snippet generate_payment_http_snippet generate_payment_status_snippet generate_payment_route_snippet snippet_nextjs_payment_route snippet_express_payment_route snippet_fastapi_payment_route snippet_laravel_payment_route snippet_go_payment_handler snippet_spring_payment_controller generate_payout_sdk_snippet generate_payout_status_snippet generate_payout_recipient_flow_snippet generate_referral_sdk_snippet generate_referral_validation_snippet generate_referral_status_snippet generate_referral_route_snippet generate_webhook_handler generate_webhook_event_router generate_mock_webhook_event generate_topup_integration_snippet explain_payram_basics explain_payram_security get_payram_links explain_payment_flow explain_payram_concepts explain_referrals_basics explain_referral_flow get_referral_dashboard_guide prepare_payram_test get_payram_doc_by_id list_payram_docs scaffold_payram_app test_payram_connection onboard_agent_setup
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-payram-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |