Для AI-агентов: markdown этой страницы — /docs/mcp-domain.mdиндекс документации — /llms.txt
MCP: domain
Обновлено
MCP: domain
Это определения инструментов из текущего ToolRegistry, включая полные inputSchema/outputSchema, scope, required_scopes (ALL), risk и версию платформы. Наличие определения не означает, что инструмент уже установлен вашим хостом или разрешён вашим credential. Обновляйте tools/list после изменения бизнеса, readiness и прав. Progressive disclosure через load_domain/describe_tool и существующий meta-dispatch описаны в MCP-руководстве. Scopes и права применяются при вызове; risk не заменяет согласие и отдельные требования денежной операции. JSON ниже — схема, а не успешный результат вызова.
domain_add_request
Attach the business's OWN domain (e.g. acme.ru) to this account for one jurisdiction zone (ru or com). Returns the TXT record the owner must publish to prove ownership, plus the next steps. ONE connection per zone: calling this again for a zone that already has one returns THAT connection unchanged (safe to retry). The domain then walks PENDING_DNS → VERIFYING → VERIFIED → ISSUING_CERT → ACTIVE — poll domain_status. The account keeps working on its technical domain the whole time.
{
"description": "Attach the business's OWN domain (e.g. acme.ru) to this account for one jurisdiction zone (`ru` or `com`). Returns the TXT record the owner must publish to prove ownership, plus the next steps. ONE connection per zone: calling this again for a zone that already has one returns THAT connection unchanged (safe to retry). The domain then walks PENDING_DNS → VERIFYING → VERIFIED → ISSUING_CERT → ACTIVE — poll `domain_status`. The account keeps working on its technical domain the whole time.",
"domain": "domain",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false,
"properties": {
"bot": {
"description": "Optional slug of the bot you expect to act on (get_active_bot). If the active bot differs, the call is refused with ACTIVE_BOT_CHANGED and nothing runs.",
"maxLength": 128,
"minLength": 1,
"type": "string"
},
"domain": {
"description": "Value for domain.",
"maxLength": 253,
"minLength": 4,
"pattern": "^(?=.{4,253}$)[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)+\\.?$",
"type": "string"
},
"storefrontLabel": {
"description": "Value for storefront Label.",
"pattern": "^[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?$",
"type": "string"
},
"zone": {
"description": "Value for zone.",
"enum": [
"ru",
"com"
],
"type": "string"
}
},
"required": [
"domain",
"zone"
],
"type": "object"
},
"name": "domain_add_request",
"outputSchema": null,
"platform_version": "1.0.19",
"required_scopes": [
"domain:write"
],
"risk": "write",
"scope": "domain:write",
"title": "Domain Add Request"
}domain_execute_unlink
Disconnect the domain identified by a matching prepared scenario. Call this tool only after final human confirmation of the prepared scenario.
{
"description": "Disconnect the domain identified by a matching prepared scenario. Call this tool only after final human confirmation of the prepared scenario.",
"domain": "domain",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false,
"properties": {
"bot": {
"description": "Optional slug of the bot you expect to act on (get_active_bot). If the active bot differs, the call is refused with ACTIVE_BOT_CHANGED and nothing runs.",
"maxLength": 128,
"minLength": 1,
"type": "string"
},
"payload_hash": {
"description": "Value for payload hash.",
"pattern": "^[a-f0-9]{64}$",
"type": "string"
},
"preparation_id": {
"description": "Value for preparation id.",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"type": "string"
}
},
"required": [
"preparation_id",
"payload_hash"
],
"type": "object"
},
"name": "domain_execute_unlink",
"outputSchema": null,
"platform_version": "1.0.19",
"required_scopes": [
"domain:write"
],
"risk": "destructive",
"scope": "domain:write",
"title": "Domain Execute Unlink"
}domain_prepare_unlink
Prepare unlinking the domain attached to one zone. The returned scenario freezes the exact current domain for human review and does not change routing. Show it to a human; only after final confirmation call domain_execute_unlink. Unlinking releases the host, stops its certificate and routing, and requires DNS verification again before a later re-attachment.
{
"description": "Prepare unlinking the domain attached to one zone. The returned scenario freezes the exact current domain for human review and does not change routing. Show it to a human; only after final confirmation call `domain_execute_unlink`. Unlinking releases the host, stops its certificate and routing, and requires DNS verification again before a later re-attachment.",
"domain": "domain",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false,
"properties": {
"bot": {
"description": "Optional slug of the bot you expect to act on (get_active_bot). If the active bot differs, the call is refused with ACTIVE_BOT_CHANGED and nothing runs.",
"maxLength": 128,
"minLength": 1,
"type": "string"
},
"zone": {
"description": "Value for zone.",
"enum": [
"ru",
"com"
],
"type": "string"
}
},
"required": [
"zone"
],
"type": "object"
},
"name": "domain_prepare_unlink",
"outputSchema": null,
"platform_version": "1.0.19",
"required_scopes": [
"domain:write"
],
"risk": "write",
"scope": "domain:write",
"title": "Domain Prepare Unlink"
}domain_status
Read where each connected domain stands: its status (PENDING_DNS / VERIFYING / VERIFIED / ISSUING_CERT / ACTIVE / FAILED), when DNS verification and the certificate landed, and — on FAILED — a human-readable reason to relay to the owner. Pass zone to narrow to one jurisdiction; omit it for all of them. This is the ONLY way to see why a connection is stuck. 0-cost read.
{
"description": "Read where each connected domain stands: its status (PENDING_DNS / VERIFYING / VERIFIED / ISSUING_CERT / ACTIVE / FAILED), when DNS verification and the certificate landed, and — on FAILED — a human-readable reason to relay to the owner. Pass `zone` to narrow to one jurisdiction; omit it for all of them. This is the ONLY way to see why a connection is stuck. 0-cost read.",
"domain": "domain",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false,
"properties": {
"zone": {
"description": "Value for zone.",
"enum": [
"ru",
"com"
],
"type": "string"
}
},
"type": "object"
},
"name": "domain_status",
"outputSchema": null,
"platform_version": "1.0.19",
"required_scopes": [
"domain:read"
],
"risk": "read",
"scope": "domain:read",
"title": "Domain Status"
}domain_verify
Check the ownership TXT record for a connected domain RIGHT NOW and, if it matches, move the domain to VERIFIED (the certificate is then issued on the first HTTPS request). Call it after telling the owner to publish the record from domain_add_request. Safe to call repeatedly: an already-verified domain answers verified: true and nothing moves. When it is not verified yet, pendingReason says WHY in the owner's terms — nxdomain (the record is not there at all), mismatch (a record with the wrong value — usually a truncated paste), ambiguous (several records, none ours — usually an old token left behind), timeout / resolver_error (their nameserver did not answer). DNS propagation is bounded by the owner's own TTL and is routinely hours, so nxdomain shortly after they publish is normal — nothing is broken. The platform also re-checks in the background, so an unattended domain still completes on its own.
{
"description": "Check the ownership TXT record for a connected domain RIGHT NOW and, if it matches, move the domain to VERIFIED (the certificate is then issued on the first HTTPS request). Call it after telling the owner to publish the record from `domain_add_request`. Safe to call repeatedly: an already-verified domain answers `verified: true` and nothing moves. When it is not verified yet, `pendingReason` says WHY in the owner's terms — `nxdomain` (the record is not there at all), `mismatch` (a record with the wrong value — usually a truncated paste), `ambiguous` (several records, none ours — usually an old token left behind), `timeout` / `resolver_error` (their nameserver did not answer). DNS propagation is bounded by the owner's own TTL and is routinely hours, so `nxdomain` shortly after they publish is normal — nothing is broken. The platform also re-checks in the background, so an unattended domain still completes on its own.",
"domain": "domain",
"inputSchema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false,
"properties": {
"bot": {
"description": "Optional slug of the bot you expect to act on (get_active_bot). If the active bot differs, the call is refused with ACTIVE_BOT_CHANGED and nothing runs.",
"maxLength": 128,
"minLength": 1,
"type": "string"
},
"zone": {
"description": "Value for zone.",
"enum": [
"ru",
"com"
],
"type": "string"
}
},
"required": [
"zone"
],
"type": "object"
},
"name": "domain_verify",
"outputSchema": null,
"platform_version": "1.0.19",
"required_scopes": [
"domain:write"
],
"risk": "write",
"scope": "domain:write",
"title": "Domain Verify"
}