NS1 MCP by usefulapi
REMOTE · NS1.USEFULAPI.IO
Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record.
Available components
Last scanned (3 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2225 tokens (~123/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://ns1.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ns1.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://ns1.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://ns1.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://ns1.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ns1.usefulapi.io/mcp |
| Authorisation server | https://ns1.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ns1.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/ns1/ |
| http (plaintext) | http://ns1.usefulapi.io/mcp | Inconclusive | 302 | http://ns1.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ns1_create_record Create DNS record ~274
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | yes | One entry per answer, each a list of rdata fields (see the tool description). |
| domain | string | yes | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| ttl | integer | – | TTL in seconds. Omit for the zone default. |
| type | string | yes | Record type. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
ns1_get_account_summary Get account summary ~43
The account's subscription, resources and utilization (queries, records, filter chains, monitors, ... against the plan limits). GET /v1/account/summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ns1_get_billing_queries Get query usage (billing) ~59
Billable DNS query usage between two Unix timestamps. GET /billing-usage/v1/queries?from=&to=.
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer | yes | Start, Unix seconds. |
| to | integer | yes | End, Unix seconds. |
No output schema declared.
No examples provided.
ns1_get_billing_records Get records usage (billing) ~39
How many DNS records the account uses against its plan limit in the current billing cycle. GET /billing-usage/v1/records.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ns1_get_data_feed Get data feed ~56
One data feed of a source by id. GET /v1/data/feeds/{source_id}/{feed_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_id | string | yes | Data feed id. |
| source_id | string | yes | Data source id. |
No output schema declared.
No examples provided.
ns1_get_data_source Get data source ~56
One data source by id with its feeds. Connection settings and credentials are redacted. GET /v1/data/sources/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | Data source id (from ns1_list_data_sources). |
No output schema declared.
No examples provided.
ns1_get_monitoring_job Get monitoring job ~65
One monitoring job by id with its configuration, rules, regions and status. Header values and credentials are redacted. GET /v1/monitoring/jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Monitoring job id (from ns1_list_monitoring_jobs). |
No output schema declared.
No examples provided.
ns1_get_qps_stats Get queries per second ~125
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}]].
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| type | string | – | Record type, e.g. A, AAAA, CNAME, MX, TXT. |
| zone | string | – | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
ns1_get_record Get record ~122
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
ns1_get_usage_stats Get query usage statistics ~280
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}]].
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Continue after this item: pass next_page.after from the previous reply. |
| aggregate | boolean | – | Sum the counts over the period. |
| domain | string | – | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| expand | boolean | – | Break the counts down further. Account and zone level only. |
| limit | integer | – | Maximum items per page, 1-1000. Omit for NS1's default page size. |
| period | string | – | Time window: 1h, 24h or 30d. Omit for the API default. |
| type | string | – | Record type, e.g. A, AAAA, CNAME, MX, TXT. |
| zone | string | – | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
ns1_get_zone Get zone ~161
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Continue after this item: pass next_page.after from the previous reply. |
| limit | integer | – | Maximum items per page, 1-1000. Omit for NS1's default page size. |
| offset | integer | – | Skip this many items: pass next_page.offset from the previous reply. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
ns1_list_data_feeds List data feeds of a source ~64
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | Data source id. |
No output schema declared.
No examples provided.
ns1_list_data_sources List data sources ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ns1_list_monitoring_jobs List monitoring jobs ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ns1_list_notify_lists List notifier lists ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ns1_list_zones List zones ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Continue after this item: pass next_page.after from the previous reply. |
| limit | integer | – | Maximum items per page, 1-1000. Omit for NS1's default page size. |
| offset | integer | – | Skip this many items: pass next_page.offset from the previous reply. |
No output schema declared.
No examples provided.
ns1_search Search zones and records ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | boolean | – | Include full record details (default true). |
| max | integer | – | Maximum results, 1-1000. |
| query | string | yes | Text to look for in zone and record names (at least 2 characters). |
| type | string | – | What to search (default all). |
No output schema declared.
No examples provided.
ns1_update_record Update DNS record ~228
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | – | The COMPLETE new answer set, each answer a list of rdata fields (as for ns1_create_record). |
| domain | string | yes | Full record name inside the zone, e.g. www.example.com (or the zone name itself for the apex). |
| ttl | integer | – | New TTL in seconds. |
| type | string | yes | Record type of the existing record. |
| zone | string | yes | Zone name, e.g. example.com. |
No output schema declared.
No examples provided.
How do I install the NS1 MCP by usefulapi server?
NS1 MCP by usefulapi is a hosted endpoint at https://ns1.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ns1.usefulapi.io
claude mcp add --transport http io-usefulapi-ns1 'https://ns1.usefulapi.io/mcp'
What is the NS1 MCP by usefulapi server?
NS1 MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ns1. Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record. This page covers its hosted endpoint (https://ns1.usefulapi.io/mcp).
Is the NS1 MCP by usefulapi server safe to use?
NS1 MCP by usefulapi scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the NS1 MCP by usefulapi server expose?
NS1 MCP by usefulapi exposes 18 tools: ns1_list_zones, ns1_get_zone, ns1_get_record, ns1_search, ns1_list_monitoring_jobs, and 13 more. Their descriptions and schemas cost roughly 2,001 tokens of context every time the server is loaded.
Does the NS1 MCP by usefulapi server require authentication?
Yes. NS1 MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the NS1 MCP by usefulapi server still maintained?
NS1 MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.