INDIVIDUAL MCP TOOL

dkim_check

Fetches and validates the DKIM public key at <selector>._domainkey.<domain>: parsed tags, key type, key size and warnings such as a revoked or malformed key.

uptimeify.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://uptimeify.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for dkim_check and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

uptimeify.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.uptimeify]
url = "https://uptimeify.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "uptimeify": {
      "type": "http",
      "url": "https://uptimeify.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: uptimeify
Remote MCP URL: https://uptimeify.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "uptimeify": {
      "url": "https://uptimeify.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "uptimeify": {
      "type": "http",
      "url": "https://uptimeify.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "uptimeify",
  "transport": "streamable-http",
  "url": "https://uptimeify.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

check_ssl — Fetches and evaluates a host's TLS certificate over a live handshake: subject, issuer, validity window, days until expiry, hostname match, chain trust, self-signed and expired flags, SANs, serial and SHA-256 fingerprint.
check_dns — Resolves a domain's DNS records in one call (A, AAAA, CNAME, MX, TXT, NS, SOA and more) and returns each record type with its values, or a per-type error where a lookup failed.
dns_propagation — Queries one domain against several public resolvers and compares the answers, which tells a recent record change apart from a stale cache.
mx_lookup — Looks up a domain's MX records and resolves each mail exchanger to its IPv4 and IPv6 addresses, ordered by priority, flagging hosts that resolve into private address space.
spf_check — Fetches a domain's SPF record and evaluates it: raw record, parsed terms with qualifiers, DNS lookups counted against the RFC 7208 limit of ten, the final `all` qualifier, and warnings for common silent failures.
dmarc_check — Fetches a domain's DMARC record from _dmarc.<domain> and evaluates it: raw record, parsed tags, policy and subdomain policy, percentage, and warnings for records that parse but offer no protection (p=none, missing rua).
dnsbl_check — Checks a public IP address against common DNS blocklists and returns, per list, whether it is listed, the list's reason code and delisting URL, plus totals and a `clean` flag.
whois — Retrieves WHOIS registration data for a domain: registrar, creation, update and expiry dates, EPP status codes, nameservers and the contact roles the registry still publishes (personal data is usually redacted).