mcp-server-subreg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBREG_URI | Yes | SOAP namespace URI, e.g. https://soap.subreg.cz/soap | |
| SUBREG_LOGIN | Yes | Subreg account login | |
| SUBREG_LOCATION | Yes | SOAP endpoint, e.g. https://soap.subreg.cz/cmd.php | |
| SUBREG_PASSWORD | Yes | Subreg account password | |
| SUBREG_READONLY | No | Set to false to allow mutating tools | true |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainC | Check whether a domain is available for registration. |
| info_domainA | Fetch registration details (status, expiration, nameservers, ...) for a domain. |
| domains_listA | List all domains held under the authenticated Subreg account. |
| pricelistB | Fetch the full TLD pricelist for the authenticated account. |
| get_pricelistB | Fetch a named/specific pricelist (e.g. a reseller pricelist). |
| get_creditA | Fetch the current account credit balance. |
| info_userA | Fetch info about the authenticated user, or a specific sub-user by id. |
| get_dns_zoneA | Fetch DNS zone records for a domain hosted on Subreg DNS. |
| info_contactA | Fetch details for a contact object by its Subreg contact id. |
| contacts_listA | List contact objects registered under the authenticated account. |
| info_orderA | Fetch the status and details of a previously submitted order. |
| get_tld_infoB | Fetch registration rules (min/max period, required fields, ...) for a TLD. |
| register_domainA | Register (order) a new domain. Requires SUBREG_READONLY=false. registrant_id/contacts_admin_id/contacts_tech_id/auth_id are Subreg contact object ids (see info_contact/contacts_list). period is in years. |
| renew_domainA | Renew an existing domain for the given number of years. Requires SUBREG_READONLY=false. |
| delete_domainB | Delete (cancel) a domain registration. Requires SUBREG_READONLY=false. |
| add_dns_recordB | Add a DNS record to a zone hosted on Subreg DNS. Requires SUBREG_READONLY=false. |
| delete_dns_recordA | Delete a DNS record from a zone by its record id. Requires SUBREG_READONLY=false. |
| create_contactA | Create a new contact object. Requires SUBREG_READONLY=false. params follows the Subreg Create_Contact schema (name, email, address, phone, etc.) — see https://subreg.cz/manual/?cmd=Create_Contact. |
| update_contactA | Update an existing contact object. Requires SUBREG_READONLY=false. params follows the Subreg Update_Contact schema — see https://subreg.cz/manual/?cmd=Update_Contact. |
| credit_correctionA | Adjust a sub-user's credit balance. Requires SUBREG_READONLY=false. amount is added to the current balance; use a negative value to subtract. |
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 20 tools
Most tools target distinct resources and actions clearly (domains, contacts, DNS, orders, credit). The only notable ambiguity is between pricelist and get_pricelist, which both fetch pricing data but are described differently enough to be mostly distinguishable.
Naming conventions are mixed: retrieval uses both get_ and info_ prefixes, list operations use noun-first names (contacts_list, domains_list), and some tools are bare nouns (pricelist). This inconsistency makes it harder to predict tool names.
With 20 tools, the server is on the heavier side, but the scope covers domain lifecycle, contacts, DNS, billing, and orders, which justifies the count. It's borderline but not excessive.
Core domain operations are present (check, register, renew, delete, list, info), plus contacts and DNS record management. However, there are notable gaps such as no delete_contact, no update_dns_record, no order listing, and no domain transfer support.