RunStack Checks MCP Server

Install RunStack Checks MCP server

claude mcp add --transport http runstack https://runstack.pro/api/mcp

{
  "mcpServers": {
    "runstack": {
      "url": "https://runstack.pro/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "runstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://runstack.pro/api/mcp"
      ]
    }
  }
}

{
  "servers": {
    "runstack": {
      "type": "http",
      "url": "https://runstack.pro/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "runstack": {
      "serverUrl": "https://runstack.pro/api/mcp"
    }
  }
}

Context tax

Connecting this server adds ~1,156 tokens of tool definitions to every model turn (moderate, 6 tools). Measured 2026-10-19 via its hosted endpoint; o200k tokenizer, worst case for clients that load all tools up front. How we measure

Input prices as of 2026-10-06. Excludes your own prompt and output.

Tools (6)

• check_tls220 tok

  Scan a public host's TLS from the internet: certificate validity, chain completeness, expiry date, hostname match, enabled protocols (TLS 1.0–1.3), cipher suites, HSTS. Use when browsers show certificate errors, before/after renewing or rotating a certificate, or to confirm old TLS versions are disabled. Use this (not check_http) for anything about the certificate or TLS configuration itself; works on any TLS port, not only 443. Returns a verdict, findings with cause and fix, and a shareable report link. Takes up to ~60 s.

• check_email_domain200 tok

  Audit a mail domain as other mail servers see it: MX, SPF (including the 10-DNS-lookup limit), DKIM, DMARC policy, PTR / forward-confirmed reverse DNS, SMTP STARTTLS on the MX hosts, MTA-STS, TLS-RPT, BIMI. Use when mail lands in spam or bounces, after changing mail provider or DNS, or before tightening DMARC. Use this (not check_dns) for any email deliverability or authentication question. Returns a verdict, findings with cause and fix, and a report link.

• check_http192 tok

  Request a public URL from outside your network and inspect the HTTP layer: status code, full redirect chain, security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy…), caching and compression headers. Use to debug redirect loops, unexpected status codes or missing headers as real visitors and CDNs see them, or to verify a web server / CDN config change after deploy. Use check_tls instead for certificate or TLS protocol questions. Returns a verdict and findings with fixes.

• check_dns177 tok

  Resolve a name at several public resolvers (Google, Cloudflare, Quad9, …) and compare their answers. Use after changing DNS records to check propagation, or when some users reach a different IP or get NXDOMAIN. Use check_email_domain instead for SPF/DKIM/DMARC analysis. Returns per-resolver answers, inconsistencies and a verdict.

• check_port151 tok

  Check from the internet whether TCP ports of a public host are open, closed or filtered. Use to verify firewall / security group rules, or to find out why a service works locally but is unreachable from outside. Only public addresses are accepted; this does not test the application behind the port (use check_http or check_tls for that).

• check_ip141 tok

  Look up an IP address or ASN: owner organization, announced prefix, PTR (reverse DNS), RPKI validity and geolocation. Use to identify who is behind an address seen in logs or headers, or to check PTR / RPKI for a mail or BGP issue. Does not test reachability (use check_port).

Freshness

Not enough public signals yet to judge maintenance.

1. Last commit (default branch)

   2026-10-18 · today · GitHub

2. Latest release

   no data · GitHub

3. Package published

   no data · npm/PyPI

4. Registry entry updated

   2026-10-17 · 1d ago · official registry · v1.0.1

How it compares in Email

Against the most-starred email servers we index. Token cost is per model turn, measured from each server's live tool list.