NS1 MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

NS1 MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 18 tools. Last commit 12 Oct 2026.

Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record.

Uptime history 5 hours of history

5 hours agonow

100.0%

Uptime 24h

17 of 17 checks

Tools

read from the server

149 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

Nothing serious here today

Today is the operative word: we check NS1 MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ns1 --transport http https://ns1.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ns1": {
      "url": "https://ns1.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.ns1]
url = "https://ns1.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ns1": {
      "url": "https://ns1.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "ns1": {
      "url": "https://ns1.usefulapi.io/mcp"
    }
  }
}

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ns1

ns1_create_record

WRITE: creates ONE new DNS record and CHANGES LIVE DNS for that name as soon as NS1 serves it; a wrong answer can take a site or mail offline. Plain records only (A, AAAA, ALIAS, CAA, CNAME, MX, PTR, SRV, TXT; no NS/SOA, no traffic-steering filters or metadata). Refuses when the record already exists (use ns1_update_record). Answers are lists of rdata fields: A ["192.0.2.10"], MX [10, "mail.example.com."], TXT ["v=spf1 -all"], SRV [10, 5, 5060, "sip.example.com."], CAA [0, "issue", "letsencrypt.org"]. PUT /v1/zones/{zone}/{domain}/{type}.

ns1_get_account_summary

The account's subscription, resources and utilization (queries, records, filter chains, monitors, ... against the plan limits). GET /v1/account/summary.

ns1_get_billing_queries

Billable DNS query usage between two Unix timestamps. GET /billing-usage/v1/queries?from=&to=.

ns1_get_billing_records

How many DNS records the account uses against its plan limit in the current billing cycle. GET /billing-usage/v1/records.

ns1_get_data_feed

One data feed of a source by id. GET /v1/data/feeds/{source_id}/{feed_id}.

ns1_get_data_source

One data source by id with its feeds. Connection settings and credentials are redacted. GET /v1/data/sources/{id}.

ns1_get_monitoring_job

One monitoring job by id with its configuration, rules, regions and status. Header values and credentials are redacted. GET /v1/monitoring/jobs/{id}.

ns1_get_qps_stats

Current queries per second for the whole account, one zone, or one record (give zone, or zone + domain + type). GET /v1/stats/qps[/{zone}[/{domain}/{type}]].

ns1_get_record

One DNS record by zone, domain and type: TTL, answers (with per-answer metadata), filter chain (traffic steering), linked record and region settings. GET /v1/zones/{zone}/{domain}/{type}.

ns1_get_usage_stats

DNS query counts for the whole account, one zone, or one record (give zone, or zone + domain + type). period is 1h, 24h or 30d; aggregate, expand, limit and after apply to the account and zone levels only (a record takes just period). If next_page is not null, call again with its after/limit. GET /v1/stats/usage[/{zone}[/{domain}/{type}]].

ns1_get_zone

One zone with its settings and its record list (each record: domain, type, TTL, short answers, linked/tier info). Large zones are paged: if next_page is not null, call again with its after/offset to get the next records. TSIG secrets are redacted. GET /v1/zones/{zone}.

ns1_list_data_feeds

List the feeds of one data source (each feed is one monitored item, e.g. one server's health) with id, name and settings. GET /v1/data/feeds/{source_id}.

ns1_list_data_sources

List the data sources (connections to third-party monitoring or custom push sources used for traffic steering): id, name, source type, status and their feeds. Connection settings and credentials are redacted. GET /v1/data/sources.

ns1_list_monitoring_jobs

List the account's NS1 monitoring jobs (health checks that feed traffic steering): id, name, type, regions, frequency, rules, current status, active flag and notify list id. Request header values and credentials are redacted. GET /v1/monitoring/jobs.

ns1_list_notify_lists

List the notifier lists that monitoring alerts are sent to: id, name and the notifier types and labels (email, Slack, PagerDuty, webhook). Notifier settings (webhook URLs, tokens, service keys, addresses) are redacted. GET /v1/lists.

ns1_list_zones

List the DNS zones in the account: name, id, TTL/SOA settings, primary/secondary setup, linked zones and tags. If next_page is not null, call again with its after/offset to get more. GET /v1/zones.

ns1_search

Search the account's zones and records by name (substring match). Returns matching zones and/or records with their answers when expand is true. GET /v1/search.

ns1_update_record

WRITE: changes ONE existing DNS record and CHANGES LIVE DNS for that name immediately. Giving answers REPLACES all current answers of the record (send the complete new set); giving only ttl changes just the TTL. Plain records only (A, AAAA, ALIAS, CAA, CNAME, MX, PTR, SRV, TXT): when answers are given, a record that uses traffic-steering filters, links or per-answer metadata is refused (edit it in the NS1 portal). Fails if the record does not exist. POST /v1/zones/{zone}/{domain}/{type}.

Endpoints

URL	Transport	State	Latency	Checked
https://ns1.usefulapi.io/mcp	streamable-http	answering	132 ms	12 min ago

Alternatives to NS1 MCP by usefulapi

same job, measured the same way

Dead Man's Snitch MCP by usefulapi

by usefulapi

Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches.

8 tools answering

Cronitor MCP by usefulapi

by usefulapi

Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.

6 tools answering

StatusPal MCP by usefulapi

by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering

Better Stack MCP by usefulapi

by usefulapi

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

9 tools answering

All Quiet MCP by usefulapi

by usefulapi

Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.

11 tools answering

updown.io MCP by usefulapi

by usefulapi

Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.

14 tools answering

Paymo MCP by usefulapi

by usefulapi

Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.

21 tools answering

Checkly MCP by usefulapi

by usefulapi

Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.

22 tools answering

NS1 MCP by usefulapi — questions

Answers built from our own checks of this server.

What can NS1 MCP by usefulapi do?

It exposes 18 tools, read directly from the server on our last check. Among them: ns1_create_record, ns1_get_account_summary, ns1_get_billing_queries, ns1_get_billing_records, ns1_get_data_feed, ns1_get_data_source and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is NS1 MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 17 of 17 checks got a reply (100.0%), average response time 149 ms. The bar chart above shows every period we have measured.

How do I connect NS1 MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does NS1 MCP by usefulapi need an API key?

No. NS1 MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is NS1 MCP by usefulapi?

It answers our handshake in 149 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is NS1 MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.