Second Brain

hostinger-mcp-dnsdeletednsrecordsv1-schema-missing-required

1 min read

Hostinger MCP DNS_deleteDNSRecordsV1 schema missing required filters field

Bug

mcp__hostinger-admin__DNS_deleteDNSRecordsV1 tool (as of 15-Apr-2026) exposes only {domain} as its parameter schema. Hostinger API requires additional filters body (array of {name, type} objects) to target deletion. Calling with only domain returns:

{"message":"The filters field is required.","errors":{"filters":["The filters field is required."]}}

Tool description explicitly mentions filters (“To filter which records to delete, add the name of the record and type to the filter”), but the JSONSchema parameters object doesn’t declare a filters property — unusable for targeted deletion.

Workarounds (worst to best)

  1. Accept orphan — if the domain no longer serves traffic (Traefik cleanup done), the A record is harmless (404 response)
  2. Manual via Hostinger UI — hpanel.hostinger.com → Domains → DNS/Nameservers
  3. DNS_updateDNSRecordsV1 with overwrite=true supplying entire zone minus the unwanted record — HIGH RISK, one typo breaks DNS for the whole zone (80+ records for arjtech.in)

Action

  • Pin issue for Hostinger MCP maintainer: schema must include filters: { type: "array", items: { name, type } }
  • For now, use workaround #2 (manual UI) for any one-off deletion

Cross-reference

error-playbook.md 15-Apr-2026 entry (diagnosis + workaround detail)

Graph View

Backlinks