Skip to content

NS1 Connect MCP by usefulapi

io.usefulapi/ns1usefulapi.iostreamable-httpv1.27.4Scanned

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

18 tools: 2 can delete or cancel things and 16 only read.

Tools: 2 delete, 0 irreversible, 0 write, 16 read.
  • Reads private data · 1
  • Reads text others write · 18
  • Can send data out · 0
  • 4 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the NS1 Connect MCP by usefulapi can do

The NS1 Connect MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (2 tools: ns1_create_record and ns1_update_record). 16 tools only read.

1 tool reads private data (ns1_list_notify_lists); 18 tools bring in text other people can write (ns1_list_zones, ns1_get_zone, ns1_get_record and 15 more).

The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.27.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Deletes or cancels 2Claude Code: deny
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_create_record" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Create DNS record
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • ns1_update_recordWRITE: changes ONE existing DNS record and CHANGES LIVE DNS for that name immediately.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_update_record" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update DNS record
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 16Show 16 read-only tools
  • ns1_get_account_summaryThe account's subscription, resources and utilization (queries, records, filter chains, monitors, ...Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_account_summary" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The account's subscription, resources and utilization (queries, records, filter chains, monitors, ... against the plan limits). GET /v1/account/summary.

    Annotations the server declares

    • title: Get account summary
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_billing_queriesBillable DNS query usage between two Unix timestamps.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_billing_queries" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Billable DNS query usage between two Unix timestamps. GET /billing-usage/v1/queries?from=&to=.

    Annotations the server declares

    • title: Get query usage (billing)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_billing_recordsHow many DNS records the account uses against its plan limit in the current billing cycle.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_billing_records" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    How many DNS records the account uses against its plan limit in the current billing cycle. GET /billing-usage/v1/records.

    Annotations the server declares

    • title: Get records usage
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_data_feedOne data feed of a source by id.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_data_feed" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One data feed of a source by id. GET /v1/data/feeds/{source_id}/{feed_id}.

    Annotations the server declares

    • title: Get data feed
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_data_sourceOne data source by id with its feeds.Reads text others write1 finding

    Why it is in this group

    • The name "ns1_get_data_source" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...with its feeds. Connection settings and credentials are redacted. GET /v1/data/sources/{id}..."

      What this check looks for
    Description, as the server wrote it
    One data source by id with its feeds. Connection settings and credentials are redacted. GET /v1/data/sources/{id}.

    Annotations the server declares

    • title: Get data source
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_monitoring_jobOne monitoring job by id with its configuration, rules, regions and status.Reads text others write1 finding

    Why it is in this group

    • The name "ns1_get_monitoring_job" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "..., regions and status. Header values and credentials are redacted. GET /v1/monitoring/jobs/{..."

      What this check looks for
    Description, as the server wrote it
    One monitoring job by id with its configuration, rules, regions and status. Header values and credentials are redacted. GET /v1/monitoring/jobs/{id}.

    Annotations the server declares

    • title: Get monitoring job
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_qps_statsCurrent queries per second for the whole account, one zone, or one record (give zone, or zone + domain + type).Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_qps_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}]].

    Annotations the server declares

    • title: Get queries per second
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_record" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get record
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_usage_statsDNS query counts for the whole account, one zone, or one record (give zone, or zone + domain + type).Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_usage_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}]].

    Annotations the server declares

    • title: Get query usage statistics
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_get_zoneOne zone with its settings and its record list (each record: domain, type, TTL, short answers, linked/tier info).Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_get_zone" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get zone
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_list_data_feedsList the feeds of one data source (each feed is one monitored item, e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_list_data_feeds" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: List data feeds
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • 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.Reads text others write1 finding

    Why it is in this group

    • The name "ns1_list_data_sources" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...nd their feeds. Connection settings and credentials are redacted. GET /v1/data/sources."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List data sources
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • 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.Reads text others write1 finding

    Why it is in this group

    • The name "ns1_list_monitoring_jobs" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...tify list id. Request header values and credentials are redacted. GET /v1/monitoring/jobs."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List monitoring jobs
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • 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).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "ns1_list_notify_lists" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List notifier lists
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ns1_list_zonesList the DNS zones in the account: name, id, TTL/SOA settings, primary/secondary setup, linked zones and tags.Reads text others writeNo findings

    Why it is in this group

    • The name "ns1_list_zones" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List zones
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://ns1.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://ns1.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

4 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://ns1.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://ns1.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.27.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ns1__ns1_list_zones",
      "mcp__ns1__ns1_get_zone",
      "mcp__ns1__ns1_get_record",
      "mcp__ns1__ns1_search",
      "mcp__ns1__ns1_list_monitoring_jobs",
      "mcp__ns1__ns1_get_monitoring_job",
      "mcp__ns1__ns1_list_notify_lists",
      "mcp__ns1__ns1_list_data_sources",
      "mcp__ns1__ns1_get_data_source",
      "mcp__ns1__ns1_list_data_feeds",
      "mcp__ns1__ns1_get_data_feed",
      "mcp__ns1__ns1_get_account_summary",
      "mcp__ns1__ns1_get_usage_stats",
      "mcp__ns1__ns1_get_qps_stats",
      "mcp__ns1__ns1_get_billing_records",
      "mcp__ns1__ns1_get_billing_queries"
    ],
    "ask": [],
    "deny": [
      "mcp__ns1__ns1_create_record",
      "mcp__ns1__ns1_update_record"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ns1. Review it before you use it.

Capability tags behind 18 rules
  • mcp__ns1__ns1_list_zones untrusted-input
  • mcp__ns1__ns1_get_zone untrusted-input
  • mcp__ns1__ns1_get_record untrusted-input
  • mcp__ns1__ns1_search untrusted-input
  • mcp__ns1__ns1_list_monitoring_jobs untrusted-input
  • mcp__ns1__ns1_get_monitoring_job untrusted-input
  • mcp__ns1__ns1_list_notify_lists private-data, untrusted-input
  • mcp__ns1__ns1_list_data_sources untrusted-input
  • mcp__ns1__ns1_get_data_source untrusted-input
  • mcp__ns1__ns1_list_data_feeds untrusted-input
  • mcp__ns1__ns1_get_data_feed untrusted-input
  • mcp__ns1__ns1_get_account_summary untrusted-input
  • mcp__ns1__ns1_get_usage_stats untrusted-input
  • mcp__ns1__ns1_get_qps_stats untrusted-input
  • mcp__ns1__ns1_get_billing_records untrusted-input
  • mcp__ns1__ns1_get_billing_queries untrusted-input
  • mcp__ns1__ns1_create_record untrusted-input
  • mcp__ns1__ns1_update_record untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/ns1/verify?hash=c032045ee3efe4ff402240a46c6db7c41f63c7c305483598a8c20c2be52aa675" | jq -e '.changed == false'

Pinned hash c032045ee3ef, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/ns1/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/ns1
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/ns1.svg)](https://radar.anlyon.com/servers/io.usefulapi/ns1)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

NS1 Connect MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NS1 Connect MCP by usefulapi safe?

No scan can promise that. What its definitions show: 18 tools, 2 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the NS1 Connect MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: ns1_create_record and ns1_update_record.

Can the NS1 Connect MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the NS1 Connect MCP by usefulapi have?

18 tools: 2 destructive, 16 read. ns1_create_record, ns1_update_record, ns1_list_zones, ns1_get_zone, ns1_get_record, ns1_search, ns1_list_monitoring_jobs, ns1_get_monitoring_job and 10 more.

Does the NS1 Connect MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the NS1 Connect MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NS1 Connect MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.