Home / MCP registry index / io.usefulapi/ns1
NS1 Connect MCP by usefulapi
io.usefulapi/ns1 in the official MCP registry.
Endpoint https://ns1.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read NS1 zones, records, monitors, data feeds and usage; create or update one DNS record.
We read its 18 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ns1_list_zones ns1_get_zone ns1_get_record ns1_search ns1_list_monitoring_jobs ns1_get_monitoring_job ns1_list_notify_lists ns1_list_data_sources ns1_get_data_source ns1_list_data_feeds ns1_get_data_feed ns1_get_account_summary ns1_get_usage_stats ns1_get_qps_stats ns1_get_billing_records ns1_get_billing_queries ns1_create_record ns1_update_record
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-ns1)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.