RunStack MCP

An official MCP server provided by RunStack that allows AI agents to perform external network diagnostics. It exposes tools to check TLS certificates, HTTP headers, email domain status, DNS records, open ports, and IP information. The server returns structured diagnoses including verdicts, findings, causes, and suggested fixes, enabling agents to monitor service health from an external perspective similar to how users or mail servers see the service.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by RunStack

MCP endpoint (Streamable HTTP)

https://runstack.pro/api/mcp

Vendor documentation

What you can do with it

Check TLS certificate validity and expiration
Verify HTTP headers and security configurations
Validate email domain DNS and deliverability
Scan for open ports and IP reputation

Tools advertised by the last live check:

check_tls
check_http
check_email_domain
check_dns
check_port
check_ip

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add runstack-mcp --url https://runstack.pro/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable runstack-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "runstack-mcp": {
      "type": "streamableHttp",
      "url": "https://runstack.pro/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start runstack-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

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

See all 1,218

Do you run RunStack MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing