Is the Domani MCP server down?

mcp-registry/run.domani/domani · v1.0.0

Also listed as glama/gwendall/domani

up · requires sign-in
Last checked 2026-10-21 05:12 UTC · handshake 1.5s

As of 2026-10-21 05:12 UTC, the Domani MCP server is up (it requires sign-in) with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
79
outages (90d)
1
tools
122

Internet identity for AI agents: register or broker domains, email, DNS - pay by card or USDC.

Install Domani MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http domani-mcp-server https://domani.run/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "domani-mcp-server": {
      "type": "http",
      "url": "https://domani.run/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (68/100)

D (68/100): 0 error(s), 5 warning(s) across 122 tool(s); ~22,733 tokens of tool definitions.
Scores higher than 4% of 15,455 MCP servers Glimind has audited.
Its tool list costs an agent ~22,733 tokens per session — more than 95% of servers.
67 → 68 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions87
Safety hints0
Token cost35
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (7)

122 of 122 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: acquire_domain, add_dnssec, add_mail_rule, add_mailbox_alias, add_suppression and 117 more

122 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

41 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: buy_aftermarket, buy_domain, cancel_backorder, cancel_broker_request, cancel_plan and 36 more

9 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: finalize_negotiation, list_mailbox_changes, respond_to_offer, update_email_messages, update_identity

Loading this server's tool list costs an agent ~22,733 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Requires authentication (Bearer); tool definitions could not be read anonymously.

If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.

Auto-fix: 96 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Frun.domani%2Fdomani/fixes

add_dnssec 1 change
{
  "name": "add_dnssec",
  "description": "Publish a DNSSEC delegation-signer (DS) record at the registry to enable DNSSEC. Get the DS values from your zone provider after signing the zone.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "domain",
      "keyTag",
      "algorithm",
      "digestType",
      "digest"
    ],
    "properties": {
      "flags": {
        "type": "string",
        "description": "Optional DNSKEY flags, e.g. 257 (KSK)"
      },
      "digest": {
        "type": "string",
        "description": "Hex digest of the DNSKEY"
      },
      "domain": {
        "type": "string",
        "description": "Domain name to enable DNSSEC for"
      },
      "keyTag": {
        "type": "string",
        "description": "Key tag, e.g. 12345"
      },
      "algorithm": {
        "type": "string",
        "description": "DNSSEC algorithm number, e.g. 13 (ECDSAP256SHA256)"
      },
      "digestType": {
        "type": "string",
        "description": "Digest type number, e.g. 2 (SHA-256)"
      },
      "maxSigLife": {
        "type": "string",
        "description": "Optional max signature life in seconds"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add DNSSEC DS Record"
}
add_mail_rule 1 change
{
  "name": "add_mail_rule",
  "description": "Add an inbound filtering rule to a mailbox. If a message matches (by from/to/subject/body), the action runs: drop, mark_read, forward (to action_arg), webhook_only (skip forward-to), or label (with action_arg). Rules run in priority order (lower first); first match wins. API: POST /api/emails/{address}/rules.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "domain",
      "slug",
      "match_field",
      "match_op",
      "match_value",
      "action"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Mailbox slug"
      },
      "action": {
        "enum": [
          "drop",
          "mark_read",
          "forward",
          "webhook_only",
          "label"
        ],
        "type": "string",
        "description": "What to do on match"
      },
      "domain": {
        "type": "string",
        "description": "Mailbox domain"
      },
      "enabled": {
        "type": "boolean",
        "description": "Default true"
      },
      "match_op": {
        "enum": [
          "contains",
          "equals",
          "regex"
        ],
        "type": "string",
        "description": "How to match"
      },
      "priority": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991,
        "description": "Lower runs first (default 0)"
      },
      "action_arg": {
        "type": "string",
        "description": "For 'forward': the destination email. For 'label': the label value."
      },
      "match_field": {
        "enum": [
          "from",
          "to",
          "subject",
          "body"
        ],
        "type": "string",
        "description": "Which field to match on"
      },
      "match_value": {
        "type": "string",
        "description": "The value/pattern to match"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add Mail Rule"
}
add_mailbox_alias 1 change
{
  "name": "add_mailbox_alias",
  "description": "Add an alias address that delivers into an existing mailbox, without using a mailbox slot. Useful for multiple public addresses (sales@, hello@, contact@) landing in one inbox. The alias must be on the same domain as the mailbox. API: POST /api/emails/{address}/aliases.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "domain",
      "slug",
      "alias"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Mailbox slug the alias delivers to, e.g. inbox"
      },
      "alias": {
        "type": "string",
        "description": "Alias address - a bare slug ('sales') or a full address on the same domain ('[email protected]')"
      },
      "domain": {
        "type": "string",
        "description": "Mailbox domain, e.g. mysite.com"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add Mailbox Alias"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/run.domani/domani"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/run.domani/domani"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Frun.domani%2Fdomani.svg)](https://glimind.com/server/mcp-registry%2Frun.domani%2Fdomani?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Frun.domani%2Fdomani?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Frun.domani%2Fdomani.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Frun.domani%2Fdomani.svg
   :target: https://glimind.com/server/mcp-registry%2Frun.domani%2Fdomani?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5aa11cc3cc13cf58…, first seen 2026-10-17, included at leaf 1435 of 37,324. Version history · verify what your client received.

Tools (122)

Compare: most reliable other servers · most reliable security servers · most reliable email servers · most reliable search servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Domani MCP server down right now?

As of 2026-10-21 05:12 UTC, the Domani MCP server is up (it requires sign-in) with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.

How many tools does Domani MCP server provide?

Domani MCP server advertises 122 tools, including acquire_domain, add_dnssec, add_mail_rule, add_mailbox_alias, add_suppression.

How do I install Domani MCP server?

Point your MCP client at this streamable-http endpoint: https://domani.run/mcp

Is the Domani MCP server safe to connect to an AI agent?

Glimind scanned all 122 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Domani MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve