PayRam Helper MCP Server
REMOTE · MCP.PAYRAM.COM · 3 COMPONENTS · SCANNED SEP 21
Remote MCP server to integrate and validate self-hosted PayRam deployments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 52 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3402 tokens (~63/item across 54 items; 52 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 52 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 54 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the PayRam Helper MCP Server server?
PayRam Helper MCP Server is a hosted endpoint at https://mcp.payram.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.payram.com
claude mcp add --transport http payram-payram-helper-mcp 'https://mcp.payram.com/mcp'
{
"mcpServers": {
"payram-payram-helper-mcp": {
"url": "https://mcp.payram.com/mcp"
}
}
} {
"servers": {
"payram-payram-helper-mcp": {
"type": "http",
"url": "https://mcp.payram.com/mcp"
}
}
} [mcp_servers.payram-payram-helper-mcp] url = "https://mcp.payram.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"payram-payram-helper-mcp": {
"type": "remote",
"url": "https://mcp.payram.com/mcp",
"enabled": true
}
}
} openclaw mcp add payram-payram-helper-mcp --url 'https://mcp.payram.com/mcp' --transport streamable-http
mcp_servers:
payram-payram-helper-mcp:
url: "https://mcp.payram.com/mcp" {
"McpServers": {
"payram-payram-helper-mcp": {
"Transport": "http",
"Url": "https://mcp.payram.com/mcp"
}
}
} assistant mcp add payram-payram-helper-mcp -t streamable-http -u 'https://mcp.payram.com/mcp'
{
"mcpServers": {
"payram-payram-helper-mcp": {
"type": "http",
"url": "https://mcp.payram.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.payram.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.payram.com | CN=YR1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | RSA 2048 | SHA256-RSA | 66c0a693a318689204f7d145e6ec7df6ced |
| SANs: mcp.payram.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.payram.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| payram.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.payram.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.payram.com/mcp | HTTPS enforced | 308 | https://mcp.payram.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
suggest_file_structure Suggest Payram File Structure ~22
Suggests a recommended backend folder/file structure for integrating Payram.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| notes | string | – | – |
| root | – | yes | – |
| title | string | yes | – |
No examples provided.
test_payram_connection Test Payram Connectivity ~113
Checks the /api/v1/payment endpoint on a Payram server using baseUrl and apiKey. If they are not provided, returns a .env template you can add to your workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Your Payram API key from the dashboard. If not provided, uses PAYRAM_API_KEY from environment. |
| baseUrl | string | – | The base URL of your Payram server (e.g., https://your-server.example). If not provided, uses PAYRAM_BASE_URL from environment. |
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | yes | – |
| errorMessage | string | – | – |
| ok | boolean | yes | – |
| payramVersion | string | – | – |
| statusCode | – | yes | – |
No examples provided.
What is the PayRam Helper MCP Server server?
PayRam Helper MCP Server is listed in the public MCP registry as io.github.PayRam/payram-helper-mcp. Remote MCP server to integrate and validate self-hosted PayRam deployments. This page covers its hosted endpoint (https://mcp.payram.com/mcp).
Is the PayRam Helper MCP Server server safe to use?
PayRam Helper MCP Server scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PayRam Helper MCP Server server expose?
PayRam Helper MCP Server exposes 52 tools: test_payram_connection, payram_doctor, generate_payment_sdk_snippet, generate_payment_http_snippet, generate_payment_status_snippet, and 47 more. Their descriptions and schemas cost roughly 3,136 tokens of context every time the server is loaded.
Does the PayRam Helper MCP Server server require authentication?
No. We connected to PayRam Helper MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayRam Helper MCP Server server still maintained?
PayRam Helper MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.