Tophost DNS MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOPHOST_API_KEY | Yes | API key configured by the tophost-dns-api instance. | |
| TOPHOST_DNS_API_URL | Yes | URL of the running tophost-dns-api instance. | |
| TOPHOST_MCP_REQUEST_TIMEOUT | No | Optional request timeout in seconds. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tophost_api_healthA | Check whether the configured Tophost DNS REST API process is reachable. |
| list_domainsA | List domains discovered by the authenticated Tophost DNS API account. |
| list_dns_recordsB | List DNS records for one Tophost domain. Optional name, type and value filters can be combined. |
| get_dns_recordA | Read one DNS record by its current Tophost record ID. |
| create_dns_recordA | Create a DNS record. The underlying API treats an already-identical record as a no-op. |
| update_dns_recordA | Update a DNS record using expected_value and expected_priority as mandatory optimistic-concurrency guards. Read the record first and pass the observed state. |
| delete_dns_recordA | Delete a DNS record using mandatory expected_value and expected_priority optimistic-concurrency guards. Read the record first and pass the observed state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action: health check, listing domains, listing/reading records, and create/update/delete operations. There is no overlap between list and get-by-ID, and update/delete are clearly separated by their optimistic-concurrency guards.
Most tools follow a clear verb_noun snake_case pattern (list/get/create/update/delete). The health check tool uses a noun-style name with a vendor prefix, which is a minor deviation, but it does not create confusion.
Seven tools is a well-scoped size for a DNS record management server: one health check, one domain enumeration tool, and a full record lifecycle. No tool feels redundant or superfluous.
The set covers the core DNS record lifecycle completely (list, get, create, update, delete) plus domain discovery and API health. There are no obvious missing operations for the stated purpose.