ClawHub

name.com registrar

v0.0.14

Domain registrar and DNS manager using the Name.com CORE API. Use when the user asks to search for, buy, or register domains, manage DNS records (A, AAAA, CN...

⭐ 1· 310·0 current·0 all-time
byPat Ramsey@patramsey
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name.com API credentials and node/npm are appropriate for a Name.com registrar/DNS management tool. The declared primary credential (NAMECOM_TOKEN) matches the described functionality (domain purchases and DNS changes).
✓
Instruction Scope
SKILL.md confines actions to domain search/registration, DNS record management, and ACME DNS-01 automation. It documents a dry-run + one-time purchaseToken flow for purchases, sandbox variables, and advises IP whitelisting. The instructions do network calls to Name.com and public DNS for propagation checks, which is expected for this purpose and is explicitly documented.
ℹ
Install Mechanism
Installation uses the npm package namecom-clawbot (node install). This is a typical choice for a Node-based MCP server but does involve fetching and installing code from the npm registry — review the npm package and linked GitHub repo before installing. The SKILL.md claims signed npm provenance (GitHub Actions) which you should verify independently.
✓
Credentials
The only required environment variables are Name.com credentials (production and optional sandbox), which are proportionate. No unrelated secrets, system config paths, or additional credentials are requested.
✓
Persistence & Privilege
always is false and the skill does not request elevated or platform-wide persistence. It runs as an MCP server process and does not claim to modify other skills or global agent settings.
Assessment
This skill appears consistent with its stated purpose, but because it will install an npm package and will have API-level access to your Name.com account, take caution before installing: 1) Inspect the npm package and GitHub repo (verify provenance/signatures) before installing. 2) Test with the sandbox credentials (NAMECOM_USERNAME_TEST / NAMECOM_TOKEN_TEST) first. 3) Use IP whitelisting on the API token and run the MCP server in an isolated environment (container/VM). 4) Be aware the token grants the ability to change DNS and register domains; prefer account credit or a low‑risk payment method and enable purchase confirmations. 5) Confirm you understand the dry-run + one-time purchaseToken flow; purchases require the token and explicit confirmation.

Like a lobster shell, security has layers — review code before you run it.

latestvk97e19pqp3z4s8x8hkpy17dhws8396tp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

Binsnode, npm
EnvNAMECOM_USERNAME, NAMECOM_TOKEN
Primary envNAMECOM_TOKEN

Install

Install namecom-clawbot MCP server (npm)
Bins: namecom-clawbot
npm i -g namecom-clawbot

Comments