Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://ns1.usefulapi.io/mcpRun this in your terminal
claude mcp add --transport http ns1 https://ns1.usefulapi.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ns1": {
"url": "https://ns1.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ns1": {
"type": "http",
"url": "https://ns1.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://ns1.usefulapi.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
ns1_list_zonesList 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_get_zoneOne 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_get_recordOne 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_searchSearch 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_list_monitoring_jobsList 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_get_monitoring_jobOne monitoring job by id with its configuration, rules, regions and status. Header values and credentials are redacted. GET /v1/monitoring/jobs/{id}.
ns1_list_notify_listsList 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_data_sourcesList 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_get_data_sourceOne data source by id with its feeds. Connection settings and credentials are redacted. GET /v1/data/sources/{id}.
ns1_list_data_feedsList 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_get_data_feedOne data feed of a source by id. GET /v1/data/feeds/{source_id}/{feed_id}.
ns1_get_account_summaryThe account's subscription, resources and utilization (queries, records, filter chains, monitors, ... against the plan limits). GET /v1/account/summary.
ns1_get_usage_statsDNS 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
ns1_get_qps_statsCurrent 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_billing_recordsHow many DNS records the account uses against its plan limit in the current billing cycle. GET /billing-usage/v1/records.
ns1_get_billing_queriesBillable DNS query usage between two Unix timestamps. GET /billing-usage/v1/queries?from=&to=.
ns1_create_recordWRITE: 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
ns1_update_recordWRITE: 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):
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 24 ms (HTTP 200)
No sign-in needed
Read 18 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.22.3) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FOGA node
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Use NS1 from Claude, Cursor, or any MCP client — zones, records, monitoring jobs, data sources and feeds, usage, QPS and billing, plus single-record writes. Hosted, no local install: connect with your own NS1 credentials.
Live endpoint: https://ns1.usefulapi.io/mcp · Homepage: https://usefulapi.io/ns1
https://ns1.usefulapi.io/mcp.claude mcp add --transport http ns1 https://ns1.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "ns1": { "url": "https://ns1.usefulapi.io/mcp" } } }
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your NS1 Connect credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/ns1/
| Tool | Type | What it does |
|---|---|---|
ns1_list_zones | read | List zones |
ns1_get_zone | read | Get zone |
ns1_get_record | read | Get record |
ns1_search | read | Search zones and records |
ns1_list_monitoring_jobs | read | List monitoring jobs |
ns1_get_monitoring_job | read | Get monitoring job |
ns1_list_notify_lists | read | List notifier lists |
ns1_list_data_sources | read | List data sources |
ns1_get_data_source | read | Get data source |
ns1_list_data_feeds | read | List data feeds of a source |
ns1_get_data_feed | read | Get data feed |
ns1_get_account_summary | read | Get account summary |
ns1_get_usage_stats | read | Get query usage statistics |
ns1_get_qps_stats | read | Get queries per second |
ns1_get_billing_records | read | Get records usage (billing) |
ns1_get_billing_queries | read | Get query usage (billing) |
ns1_create_record | write | Create DNS record |
ns1_update_record | write | Update DNS record |
ns1_usage_status | meta | Usage status (free-tier meter) |
ns1_request_feature | meta | Request a missing feature |
ns1_upgrade | meta | Upgrade to Pro or Pro+ |
ns1_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this server only. Subscribe with ns1_upgrade (it returns a Stripe Checkout link). Cancel any time with ns1_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running ns1_upgrade before then undoes the cancel. Or write to support@usefulapi.io.
MIT © usefulapi. Not affiliated with or endorsed by NS1.