Server providing Argo CD integration for MCP clients.
LWS 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.
What it does
Manage LWS (lws.fr) domains, DNS zones, hosting and account from any MCP client.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'LWS_LOGIN=${LWS_LOGIN}' --env 'LWS_API_KEY=${LWS_API_KEY}' --transport stdio lws-mcp '--' uvx lws-mcp
# 2 — ask your agent for something these tools do
# get_domain, check_domain_availability, list_tlds and 27 more
It needs LWS_LOGIN, LWS_API_KEY: this reads them from your environment, so export them first.
LWS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts LWS as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads LWS_LOGIN (Your LWS account ID (the digits of LWS-XXXXXX)), LWS_API_KEY (LWS API key (LWS Panel > Api LWS)) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx LWS_LOGIN …, setx LWS_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'LWS_LOGIN=${LWS_LOGIN}' --env 'LWS_API_KEY=${LWS_API_KEY}' --transport stdio lws-mcp '--' uvx lws-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: LWS_LOGIN — Your LWS account ID (the digits of LWS-XXXXXX); LWS_API_KEY — LWS API key (LWS Panel > Api LWS). You set them in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
30 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.
Get a domain's owner, nameservers and status flags (redemption, hold, transfer lock).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — |
Check whether a domain name is free to register (data is true when available).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — |
List the extensions LWS sells with their purchase, renewal, transfer and restore prices (EUR).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tld | string | no | Only return this extension, e.g. '.fr' or 'fr' |
Replace the four nameservers of a domain (deferred: see list_pending_requests).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| ns1 | yes | — | |
| ns2 | yes | — | |
| ns3 | yes | — | |
| ns4 | yes | — |
Lock or unlock the transfer of a domain to another registrar (deferred).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| enabled | boolean | yes | true to lock transfers, false to allow them |
Have the transfer authorization code e-mailed to the domain owner (deferred).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — |
Redirect a whole domain to a URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| url | string | yes | Destination URL |
| type | integer | no | 301 permanent, 302 temporary |
Remove a domain's redirection (succeeds even if there was none).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — |
Get the remaining balance of the prepaid account, in EUR.
No parameter schema on file.
List every purchase, renewal and other transaction made through the API.
No parameter schema on file.
List the contacts managed by the account, keyed by contact ID.
No parameter schema on file.
Get a contact's details (name, address, e-mail, phone, credit).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact | yes | — |
Create a contact managed by the account, usable as owner of domains and hostings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firstname | string | yes | — |
| lastname | string | yes | — |
| string | yes | — | |
| phone | yes | — | |
| address | string | yes | — |
| postal | string | yes | — |
| city | string | yes | — |
| country | yes | — | |
| password | yes | — | |
| company | string | no | Leave empty for an individual |
Update a contact's address, phone or password. Only the fields given are changed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact | yes | — | |
| address | string | no | — |
| postal | string | no | — |
| city | string | no | — |
| country | no | — | |
| phone | no | — | |
| password | no | — |
TEST ENVIRONMENT ONLY: add fake credit to a contact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact | yes | — | |
| amount | yes | — |
TEST ENVIRONMENT ONLY: add fake credit to your own (reseller) account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | yes | — |
List the DNS records of a domain (id, type, name, value, ttl). Use the ids to update or delete records.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| type | no | Only return records of this type | |
| name | string | no | Only return records with this name ('@', 'www'...) |
Check whether a DNS change is live: what is saved in the LWS zone, what the domain's nameservers answer, and what three public resolvers (Cloudflare, Google, Quad9) answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Fully qualified name to look up, e.g. _dmarc.example.fr |
| type | no | Record type to look up | |
| expected | string | no | Value you expect to see; by default, what is saved in the LWS zone |
Add a record to a domain's DNS zone. Propagation can take up to a few hours.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| type | yes | — | |
| name | yes | — | |
| value | yes | — | |
| ttl | no | — |
Replace an existing DNS record. Every field is required; LWS adds the record if the id does not exist.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| id | yes | — | |
| type | yes | — | |
| name | yes | — | |
| value | yes | — | |
| ttl | no | — |
Delete a DNS record. Check the id with get_dns_zone first: a wrong record can take a site or mail down.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| id | yes | — |
List every domain and hosting on the account, with expiry dates, nameservers and auto-renewal.
No parameter schema on file.
Get a hosting's package, purchase and expiry dates, nameservers and auto-renewal settings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hosting | yes | — |
List every hosting package with its monthly price in EUR.
No parameter schema on file.
Get the renewal price (hosting, domain, options) and the expiry status. Check it before renew_hosting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hosting | yes | — |
Turn automatic renewal of a hosting (and its domain, if bought at LWS) on or off.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hosting | yes | — | |
| enabled | boolean | yes | — |
PAID: buy a domain and/or hosting, debited from the prepaid account (deferred).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| package | string | yes | Package name from list_hosting_prices, or 'domaine' to buy only the domain |
| owner | integer | yes | LWS contact ID that will own it (see list_contacts) |
| type | string | no | buy: hosting + new domain; host: hosting for a domain you own; transfer: move in |
| period | integer | no | Duration in months |
PAID: renew a hosting and its domain for another period, debited from the prepaid account (deferred).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hosting | yes | — |
Search the requests made through the API. 'retour' stays empty until a deferred request is processed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | no | Endpoint family, e.g. 'domain' or 'hosting' |
| value | string | no | Domain or hosting the request was about |
| subtype | string | no | Endpoint subtype, e.g. 'dns' |
List the deferred requests that have not been processed yet.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 LWS or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (30 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
2 of the 30 recovered tools are registered only when settings.allows_writes holds (src/lws_mcp/tools/account.py:42) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 15.
2 of the 30 recovered tools are registered only when settings.test_mode holds (src/lws_mcp/tools/account.py:95) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 15.
3 of the 30 recovered tools are registered only when not settings.allows_writes is false (src/lws_mcp/tools/dns.py:124) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 15.
5 of the 30 recovered tools are registered only when not settings.allows_writes is false (src/lws_mcp/tools/domains.py:39) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 15.
3 of the 30 recovered tools are registered only when not settings.allows_writes is false (src/lws_mcp/tools/hosting.py:42) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 15.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
15 tools are registered unconditionally · (1) 2 more only when settings.allows_writes holds (src/lws_mcp/tools/account.py:42) · (2) 2 more only when settings.test_mode holds (src/lws_mcp/tools/account.py:95) · (3) 3 more only when not settings.allows_writes is false (src/lws_mcp/tools/dns.py:124) · (4) 5 more only when not settings.allows_writes is false (src/lws_mcp/tools/domains.py:39) · (5) 3 more only when not settings.allows_writes is false (src/lws_mcp/tools/hosting.py:42) — typically when a key or option is configured. All 30 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_account_balance | no tags | |
| get_purchase_history | no tags | |
| list_contacts | no tags | |
| get_contact | no tags | |
| create_contact conditional (1) | external-sink | external-sink: handler sends an HTTP POST (request("POST", …)) at src/lws_mcp/tools/account.py:70 |
| update_contact conditional (1) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/account.py:92 |
| add_test_credit_to_contact conditional (2) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/account.py:100 |
| add_test_credit_to_account conditional (2) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/account.py:105 |
| get_dns_zone | no tags | |
| check_dns_propagation | no tags | |
| add_dns_record conditional (3) | external-sink | external-sink: handler sends an HTTP POST (request("POST", …)) at src/lws_mcp/tools/dns.py:133 |
| update_dns_record conditional (3) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/dns.py:150 |
| delete_dns_record conditional (3) | external-sink | external-sink: handler sends an HTTP DELETE (request("DELETE", …)) at src/lws_mcp/tools/dns.py:156 |
| get_domain | no tags | |
| check_domain_availability | no tags | |
| list_tlds | no tags | |
| update_nameservers conditional (4) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/domains.py:52 |
| set_transfer_protection conditional (4) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/domains.py:60 |
| request_transfer_authcode conditional (4) | no tags | |
| create_domain_redirect conditional (4) | external-sink | external-sink: handler sends an HTTP POST (request("POST", …)) at src/lws_mcp/tools/domains.py:74 |
| delete_domain_redirect conditional (4) | external-sink | external-sink: handler sends an HTTP DELETE (request("DELETE", …)) at src/lws_mcp/tools/domains.py:79 |
| list_hostings | no tags | |
| get_hosting | no tags | |
| list_hosting_prices | no tags | |
| get_renewal_prices | no tags | |
| set_auto_renew conditional (5) | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at src/lws_mcp/tools/hosting.py:48 |
| buy_hosting conditional (5) | external-sink | external-sink: handler sends an HTTP POST (request("POST", …)) at src/lws_mcp/tools/hosting.py:71 |
| renew_hosting conditional (5) | external-sink | external-sink: handler sends an HTTP POST (request("POST", …)) at src/lws_mcp/tools/hosting.py:79 |
| list_requests | no tags | |
| list_pending_requests | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish LWS can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.