MCP server (Model Context Protocol) over JSON-RPC 2.0

POST /mcp

Stateless MCP endpoint (Streamable HTTP transport) for AI assistants. Send JSON-RPC 2.0 messages; methods: initialize, tools/list, tools/call, ping. Every check is exposed as a tool (dns_health_check, dns_lookup, dns_propagation, domain_availability, dkim_check, dnssec_check, mail_check, seo_check, idn_convert, generate_record) calling the same engine as the REST endpoints, with the same auth and rate limits. In Claude, add as a connector with URL https://dns-doctor.com/mcp. This is JSON-RPC, not REST: the schemas below are a generic JSON-RPC envelope.

Request body

Field	Type	Required	Description
`jsonrpc`	`string`	yes	(`2.0`)
`id`	`unknown`	no	Request id (string or number). Omit for notifications.
`method`	`string`	yes	(`initialize`, `tools/list`, `tools/call`, `ping`)
`params`	`object`	no	—

Responses

Status	Type	Description
`200`	`object`	JSON-RPC 2.0 response
`202`	—	Accepted (notifications get no response body)
`413`	`object`	Error

Example

curl -X POST "https://dns-doctor.com/mcp" \
  -H "Authorization: Bearer $REGFISH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": null,
    "method": "initialize",
    "params": null
  }'

Build a request

Fill in values — the call below updates as you type. Nothing is sent: the API does not currently allow browser requests from this domain (CORS). The API key is not stored.