Skip to content
Back to search

rdpmonster-mcp

RDPMonster MCP server

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/klovbin--rdpmonster-mcp/badge.svg)](/listings/klovbin--rdpmonster-mcp)

HTML

<a href="/listings/klovbin--rdpmonster-mcp"><img src="/api/listings/klovbin--rdpmonster-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requirements: Node.js **18** or newer.

git clone https://github.com/klovbin/rdpmonster-mcp.git
cd rdpmonster-mcp
npm install

Add the server to your MCP client configuration. Replace the path with the absolute project path:

{
  "mcpServers": {
    "rdpmonster": {
      "command": "node",
      "args": ["/absolute/path/to/rdpmonster-mcp/src/index.js"],
      "env": {
        "RDPMONSTER_EMAIL": "you@example.com",
        "RDPMONSTER_PASSWORD": "your-password"
      }
    }
  }
}

Or omit `env` and use files:

mkdir -p ~/.config/rdpmonster-mcp
printf '%s' 'you@example.com' > ~/.config/rdpmonster-mcp/email
printf '%s' 'your-password' > ~/.config/rdpmonster-mcp/password
chmod 600 ~/.config/rdpmonster-mcp/email ~/.config/rdpmonster-mcp/password

Override the config directory with `RDPMONSTER_MCP_CRED_DIR`. Email also accepts `RDPMONSTER_USERNAME`.

The MCP server communicates over standard input/output. Diagnostic messages from CLI smoke scripts go to stderr; the server itself is quiet on stdout except MCP framing.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 168 lines
  1. # RDP Monster MCP
  2. > WHMCS client-area automation for [manager.rdp.monster](https://manager.rdp.monster) — login, register, stay authenticated.
  3. RDP Monster MCP talks to the live WHMCS panel over HTTPS with a cookie-jar HTTP session. It logs in with existing credentials, registers new client accounts, and reports whether the in-process session is still authenticated. No browser is required: CSRF tokens are scraped from the login/register HTML, forms are posted as `application/x-www-form-urlencoded`, and cookies stay in MCP process memory for follow-up calls until the process restarts. Credentials resolve from tool arguments, environment variables, or small files under `~/.config/rdpmonster-mcp/` so agents can rotate accounts without baking secrets into the config.
  4. ## What it does
  5. - Authenticates against `https://manager.rdp.monster/login` and confirms access to the client area.
  6. - Registers new WHMCS clients via `/register.php` (firstname, lastname, email, country, password).
  7. - Keeps the authenticated cookie session in memory for subsequent tools in the same MCP process.
  8. - Reports session health without re-entering credentials (`status`).
  9. - Resolves email/password from tool args → env → config files, so multi-account vaults (e.g. Infisical) can feed the server at call time.
  10. JavaScript-rendered pages are **not** required. Cloudflare challenges, CAPTCHAs, or form markup changes will surface as missing CSRF tokens or rejected redirects.
  11. ## MCP tools
  12. | Tool | Purpose |
  13. | --- | --- |
  14. | `login` | Log in to manager.rdp.monster. Optional `email` / `password`; otherwise uses env or `~/.config/rdpmonster-mcp/{email,password}`. Starts a fresh HTTP session and keeps cookies in memory. |
  15. | `register` | Create a new WHMCS account (`email`, `password` required; optional `firstname`, `lastname`, `country`). On success the process session is already logged in. |
  16. | `list_services` / `get_my_services` | List products/services for the logged-in account with `status`, pricing, next due date, dedicated IP. Optional `status` filter (`Active`, `Pending`, …). Requires `login` first. |
  17. | `get_service` | Product details by service id: IP, username, OS, billing fields, status. |
  18. | `get_connection` | Connection hint (`host`, `port`, `protocol`, `username`, `password` if the panel exposes Cloud-Init Password). |
  19. | `list_invoices` / `get_my_invoices` | List invoices with totals and statuses (`Paid`, `Unpaid`, `Cancelled`, …). Optional `status` filter. |
  20. | `list_tariffs` | Catalog of store tariffs (group, slug, priceFrom, specs). Optional `group` filter. |
  21. | `get_tariff_options` | Configure options for one slug: billing cycles, OS, disk, extra IPv4. |
  22. | `create_order` | Put `items[]` into the WHMCS cart (`qty`, `billingcycle`, `os`, `disk`, `maxPrice` / `exactPrice`). Does **not** pay. Requires `login`. |
  23. | `status` | Check whether the current in-memory session is still authenticated. Returns `reason: "no_session"` if `login` / `register` was never called. |
  24. All tools return a JSON text payload (`ok`, identity fields, and error messages on failure). `login` and `register` replace any previous session in the process.
  25. ### Session reuse
  26. `login` and `register` own the process-wide cookie jar. Consecutive `status` calls reuse that jar — no re-login. Restarting the MCP server (or a failed login/register) clears the session. There is no disk-backed cookie store.
  27. ### Credentials that write files
  28. This server does **not** write credentials. Put secrets in env, config files you manage, or an external vault. `register` creates a real panel account — store that password outside the repo.
  29. ## Quick start
  30. Requirements: Node.js **18** or newer.
  31. ```bash
  32. git clone https://github.com/klovbin/rdpmonster-mcp.git
  33. cd rdpmonster-mcp
  34. npm install
  35. ```
  36. Add the server to your MCP client configuration. Replace the path with the absolute project path:
  37. ```json
  38. {
  39. "mcpServers": {
  40. "rdpmonster": {
  41. "command": "node",
  42. "args": ["/absolute/path/to/rdpmonster-mcp/src/index.js"],
  43. "env": {
  44. "RDPMONSTER_EMAIL": "you@example.com",
  45. "RDPMONSTER_PASSWORD": "your-password"
  46. }
  47. }
  48. }
  49. }
  50. ```
  51. Or omit `env` and use files:
  52. ```bash
  53. mkdir -p ~/.config/rdpmonster-mcp
  54. printf '%s' 'you@example.com' > ~/.config/rdpmonster-mcp/email
  55. printf '%s' 'your-password' > ~/.config/rdpmonster-mcp/password
  56. chmod 600 ~/.config/rdpmonster-mcp/email ~/.config/rdpmonster-mcp/password
  57. ```
  58. Override the config directory with `RDPMONSTER_MCP_CRED_DIR`. Email also accepts `RDPMONSTER_USERNAME`.
  59. The MCP server communicates over standard input/output. Diagnostic messages from CLI smoke scripts go to stderr; the server itself is quiet on stdout except MCP framing.
  60. ## Connect an MCP client (Cursor)
  61. Same shape as above in `~/.cursor/mcp.json` (or project MCP config). Reload MCP after edits. Call `login` or `register` once per process lifetime before any tool that needs an authenticated session.
  62. ## Example calls
  63. Login with explicit credentials:
  64. ```json
  65. {
  66. "email": "tokyo.decoy874@passinbox.com",
  67. "password": "••••••••"
  68. }
  69. ```
  70. Login from env / config files (no args):
  71. ```json
  72. {}
  73. ```
  74. Register a new account:
  75. ```json
  76. {
  77. "email": "new.alias@passinbox.com",
  78. "password": "••••••••",
  79. "firstname": "Tokyo",
  80. "lastname": "Decoy",
  81. "country": "US"
  82. }
  83. ```
  84. `country` is an ISO-3166 alpha-2 code (default `US`). Password minimum length is **5** (WHMCS panel rule).
  85. Check session:
  86. ```json
  87. {}
  88. ```
  89. ## Development
  90. ```bash
  91. # smoke login (args or config files)
  92. npm run login:test -- user@example.com 'password'
  93. # register + fresh-session login verify
  94. npm run register:test -- new@example.com 'password' First Last US
  95. # run MCP over stdio
  96. npm start
  97. ```
  98. ### Layout
  99. ```
  100. src/
  101. index.js MCP server (stdio)
  102. login.js WHMCS login
  103. register.js WHMCS register
  104. session.js cookie-jar fetch wrapper
  105. credentials.js env / config resolution
  106. constants.js base URLs
  107. scripts/
  108. login-test.js
  109. register-test.js
  110. ```
  111. ## Roadmap
  112. - Optional Infisical-backed multi-account picker as a first-class tool
  113. - Reveal Cloud-Init password when the panel exposes it via module AJAX
  114. - Complete checkout / pay invoice helpers (create_order currently stops at cart)
  115. ## Practical limitations
  116. - Authentication beyond form login (2FA, CAPTCHA, Cloudflare interstitial) is not bypassed.
  117. - Markup or CSRF field renames on manager.rdp.monster will break token extraction until updated.
  118. - Session cookies exist only in the MCP process; they are lost on restart and are not shared across parallel server instances.
  119. - `register` hits the live panel — duplicate emails and weak passwords are rejected by WHMCS, not by local validation beyond length.
  120. - Cloud-Init / root password is often empty in the product HTML; `get_connection` returns `password: null` and a note when that happens.
  121. - Invoice and service `status` filters are applied client-side (the panel query string does not narrow the table).
  122. ## License
  123. Repository — [klovbin/rdpmonster-mcp](https://github.com/klovbin/rdpmonster-mcp).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.