Server providing Argo CD integration for MCP clients.
Nothing to run from here
NS1 MCP by usefulapi 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.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ns1-mcp-by-usefulapi https://ns1.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# ns1_list_zones, ns1_get_zone, ns1_get_record and 15 more
NS1 MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ns1-mcp-by-usefulapi https://ns1.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 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.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum items per page, 1-1000. Omit for NS1's default page size. |
| after | string | no | Continue after this item: pass next_page.after from the previous reply. |
| offset | integer | no | Skip this many items: pass next_page.offset from the previous reply. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Zone name, e.g. example.com. |
| limit | integer | no | Maximum items per page, 1-1000. Omit for NS1's default page size. |
| after | string | no | Continue after this item: pass next_page.after from the previous reply. |
| offset | integer | no | Skip this many items: pass next_page.offset from the previous reply. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Zone name, e.g. example.com. |
| domain | string | yes | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| type | string | yes | Record type, e.g. A, AAAA, CNAME, MX, TXT. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Text to look for in zone and record names (at least 2 characters). |
| type | string | no | What to search (default all). |
| expand | boolean | no | Include full record details (default true). |
| max | integer | no | Maximum results, 1-1000. |
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.
No parameter schema on file.
One monitoring job by id with its configuration, rules, regions and status. Header values and credentials are redacted. GET /v1/monitoring/jobs/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | Monitoring job id (from ns1_list_monitoring_jobs). |
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.
No parameter schema on file.
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.
No parameter schema on file.
One data source by id with its feeds. Connection settings and credentials are redacted. GET /v1/data/sources/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_id | string | yes | Data source id (from ns1_list_data_sources). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_id | string | yes | Data source id. |
One data feed of a source by id. GET /v1/data/feeds/{source_id}/{feed_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source_id | string | yes | Data source id. |
| feed_id | string | yes | Data feed id. |
The account's subscription, resources and utilization (queries, records, filter chains, monitors, ... against the plan limits). GET /v1/account/summary.
No parameter schema on file.
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}]].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | no | Zone name, e.g. example.com. |
| domain | string | no | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| type | string | no | Record type, e.g. A, AAAA, CNAME, MX, TXT. |
| period | string | no | Time window: 1h, 24h or 30d. Omit for the API default. |
| aggregate | boolean | no | Sum the counts over the period. |
| expand | boolean | no | Break the counts down further. Account and zone level only. |
| limit | integer | no | Maximum items per page, 1-1000. Omit for NS1's default page size. |
| after | string | no | Continue after this item: pass next_page.after from the previous reply. |
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}]].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | no | Zone name, e.g. example.com. |
| domain | string | no | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| type | string | no | Record type, e.g. A, AAAA, CNAME, MX, TXT. |
How many DNS records the account uses against its plan limit in the current billing cycle. GET /billing-usage/v1/records.
No parameter schema on file.
Billable DNS query usage between two Unix timestamps. GET /billing-usage/v1/queries?from=&to=.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | integer | yes | Start, Unix seconds. |
| to | integer | yes | End, Unix seconds. |
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.exampl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Zone name, e.g. example.com. |
| domain | string | yes | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| type | string | yes | Record type. |
| answers | array | yes | One entry per answer, each a list of rdata fields (see the tool description). |
| ttl | integer | no | TTL in seconds. Omit for the zone default. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Zone name, e.g. example.com. |
| domain | string | yes | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| type | string | yes | Record type of the existing record. |
| answers | array | no | The COMPLETE new answer set, each answer a list of rdata fields (as for ns1_create_record). |
| ttl | integer | no | New TTL in seconds. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 NS1 MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish NS1 MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.