Home / MCP registry index / com.nymwell/mcp

Nymwell

com.nymwell/mcp in the official MCP registry. Endpoint https://nymwell.com/mcp.

The registry describes it as: Look up and buy domain names: live prices, any domain's public records, renewals, transfers and DNS.

We read its 54 tools on 2026-10-31. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http nymwell https://nymwell.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "nymwell": {
      "url": "https://nymwell.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"nymwell","type":"http","url":"https://nymwell.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

nymwell_status list_domains list_dns_records list_invoices list_members list_audit_events check_domain_eligibility stage_dns_change search_domains screen_domains domain_info get_quote purchase_domain get_order list_dns_presets apply_dns_preset suggest_domains get_tld_info get_domain set_auto_renew update_domain_settings set_nameservers set_contacts request_auth_code cancel_registration list_domain_services change_domain_service list_transfers cancel_transfer list_unverified_contacts get_registrant list_approvals resend_contact_verification get_dashboard list_orders submit_transfer check_domain track_domain apply_dns_to_domains undo_dns_apply dns_templates dns_zone_file set_record_note set_domain_tags domain_page managed_domain_plan workspace_defaults domain_moves decide_approval save_registrant manage_members manage_api_keys connected_apps contact_support

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): bdc5a8cce2134c7a. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-nymwell-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-nymwell-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.