Home / MCP registry index / io.usefulapi/dnsimple
DNSimple MCP by usefulapi
io.usefulapi/dnsimple in the official MCP registry.
Endpoint https://dnsimple.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: MCP server for DNSimple — domains, DNS zone records, availability, pricing and contacts.
We read its 12 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
dnsimple_whoami dnsimple_list_domains dnsimple_get_domain dnsimple_list_zone_records dnsimple_get_zone_record dnsimple_check_domain dnsimple_get_domain_prices dnsimple_list_zones dnsimple_list_contacts dnsimple_create_zone_record dnsimple_update_zone_record dnsimple_delete_zone_record
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-dnsimple)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.