Skip to main content
Glama
mcp-server-subreg

mcp-server-subreg

mcp-server-subreg

mcp-server-subreg

M8ven Verified

MCP server exposing the Subreg.cz domain registrar SOAP API — via the subreg-client library — as tools for LLM agents built with FastMCP.

Configuration

Credentials are read from the environment only, never accepted as tool parameters. Copy the template and fill in real values:

cp .env.example .env
# edit .env — never commit .env

Variable

Required

Description

SUBREG_LOCATION

yes

SOAP endpoint, e.g. https://soap.subreg.cz/cmd.php

SUBREG_URI

yes

SOAP namespace URI, e.g. https://soap.subreg.cz/soap

SUBREG_LOGIN

yes

Subreg account login

SUBREG_PASSWORD

yes

Subreg account password

SUBREG_READONLY

no

true (default) blocks mutating tools; set to false to allow domain/DNS/contact/billing writes

Use https://ote-soap.subreg.cz/... endpoints for Subreg's OTE sandbox environment while testing writes. Prefer OTE (or a disposable account) for any SUBREG_READONLY=false session — never mutate production domains from an agent.

Related MCP server: mcp-namecheap

Tools

Read-only: check_domain, info_domain, domains_list, pricelist, get_pricelist, get_credit, users_list, info_user, get_dns_zone, info_contact, contacts_list, info_order, get_tld_info.

Mutating (require SUBREG_READONLY=false): register_domain, renew_domain, delete_domain, add_dns_record, delete_dns_record, create_contact, update_contact, credit_correction.

info_user requires a numeric sub-user id (discover via users_list). Subreg's Info_User rejects an empty payload.

Usage

pip install -e .
export SUBREG_LOCATION=https://soap.subreg.cz/cmd.php
export SUBREG_URI=https://soap.subreg.cz/soap
export SUBREG_LOGIN=...
export SUBREG_PASSWORD=...
export SUBREG_READONLY=true
mcp-server-subreg

Development

pytest

Live capability scenario

Exercises every read tool against a real Subreg SOAP account and verifies that mutating tools refuse under SUBREG_READONLY=true:

export SUBREG_LOCATION=https://soap.subreg.cz/cmd.php
export SUBREG_URI=https://soap.subreg.cz/soap
export SUBREG_LOGIN=...
export SUBREG_PASSWORD=...
export SUBREG_READONLY=true
python tests/live_capability_scenario.py --json-out /tmp/subreg-live.json

--allow-writes is refused against production soap.subreg.cz (use OTE).

Available Tools

20 tools
add_dns_recordAdd Dns RecordB

Add a DNS record to a zone hosted on Subreg DNS. Requires SUBREG_READONLY=false.

Inputs: name (required), type (required), domain (required), content (required), +2 more.

check_domainCheck DomainC

Check whether a domain is available for registration.

Inputs: domain (required).

contacts_listContacts ListA

List contact objects registered under the authenticated account.

Inputs: no named parameters.

create_contactCreate 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.

Inputs: params (required).

credit_correctionCredit 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.

Inputs: amount (required), reason (required), username (required).

delete_dns_recordDelete Dns RecordA

Delete a DNS record from a zone by its record id. Requires SUBREG_READONLY=false.

Inputs: domain (required), record_id (required).

delete_domainDelete DomainB

Delete (cancel) a domain registration. Requires SUBREG_READONLY=false.

Inputs: domain (required).

domains_listDomains ListA

List all domains held under the authenticated Subreg account.

Inputs: no named parameters.

get_creditGet CreditA

Fetch the current account credit balance.

Inputs: no named parameters.

get_dns_zoneGet Dns ZoneA

Fetch DNS zone records for a domain hosted on Subreg DNS.

Inputs: domain (required).

get_pricelistGet PricelistB

Fetch a named/specific pricelist (e.g. a reseller pricelist).

Inputs: pricelist (required).

get_tld_infoGet Tld InfoB

Fetch registration rules (min/max period, required fields, ...) for a TLD.

Inputs: tld (required).

info_contactInfo ContactA

Fetch details for a contact object by its Subreg contact id.

Inputs: contact_id (required).

info_domainInfo DomainA

Fetch registration details (status, expiration, nameservers, ...) for a domain.

Inputs: domain (required).

info_orderInfo OrderA

Fetch the status and details of a previously submitted order.

Inputs: order_id (required).

info_userInfo UserA

Fetch info about the authenticated user, or a specific sub-user by id.

Inputs: user_id.

pricelistPricelistB

Fetch the full TLD pricelist for the authenticated account.

Inputs: no named parameters.

register_domainRegister 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.

Inputs: domain (required), auth_id (required), registrant_id (required), contacts_tech_id (required), +4 more.

renew_domainRenew DomainA

Renew an existing domain for the given number of years. Requires SUBREG_READONLY=false.

Inputs: domain (required), years.

update_contactUpdate 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.

Inputs: params (required), contact_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 20 tools

    Disambiguation4/5

    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 Consistency2/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for domain intelligence — WHOIS, DNS records, SSL certificate inspection, SPF/DMARC validation, security-header audits, and blacklist/reputation checks, callable by AI agents. Powered by domainintel.app; runs server-side, no local setup.
      7
      71 npm
      MIT