How do I install Runstack?

Runstack is a remote plugin. You do not need to install anything locally. Add the server URL to your AI app's MCP configuration and you are ready to go.

Is Runstack safe to use?

Yes. Runstack passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What AI apps work with Runstack?

Runstack uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Runstack MCP Server

by WithoutCowards

Developer ToolsLow Risk10.0MCP RegistryRemote

Free

Server data from the Official MCP Registry

External checks of TLS, HTTP headers, email domain, DNS and ports, with cause and fix

About

External checks of TLS, HTTP headers, email domain, DNS and ports, with cause and fix

Remote endpoints: streamable-http: https://runstack.pro/api/mcp

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

6 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

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

Documentation

View on GitHub

From the project's GitHub README.

RunStack MCP — external infrastructure checks for AI agents

Remote MCP server that checks your public infrastructure from the outside — the way users, browsers and other mail servers see it — and returns a diagnosis: verdict, findings with cause and fix, and a shareable report link.

Nothing runs locally and nothing runs on your servers: only public data is checked.

Endpoint: https://runstack.pro/api/mcp (Streamable HTTP, stateless)
Auth: header X-RunStack-Key: rsk_... (or Authorization: Bearer rsk_...)
Free key: https://runstack.pro/account — 200 calls/day
Registry name: pro.runstack/checks

Tools

Tool	What it checks
`check_tls`	Certificate validity and chain, expiry, hostname, TLS 1.0–1.3, ciphers, HSTS
`check_http`	Status, redirect chain, security headers (HSTS, CSP, X-Frame-Options…), caching, compression
`check_email_domain`	MX, SPF (10-lookup limit), DKIM, DMARC, PTR/FCrDNS, STARTTLS, MTA-STS, TLS-RPT, BIMI
`check_dns`	Answers from several public resolvers compared — propagation, NXDOMAIN, inconsistencies
`check_port`	TCP ports open / closed / filtered from the internet
`check_ip`	IP or ASN owner, prefix, PTR, RPKI, geolocation

All tools are read-only.

Example (abridged, real output)

"Check the mail setup of runstack.ru"

FAIL: Mail domain runstack.ru: critical issues
- MX: 10 mxs1.reg.ru, 20 mxs2.reg.ru
- SPF: ~all · lookups 4/10
- DMARC: p=none
- DKIM: dkim

Findings:
- [error] Multiple DMARC records
  why: _dmarc.runstack.ru has 2 v=DMARC1 records — receivers then ignore DMARC entirely. Keep one.
  how-to: https://runstack.ru/docs/fix-dmarc-p-none
- [info] SPF ~all (softfail)
  why: Soft fail — common during monitoring.
- [info] MX certificate not valid for the server name
  why: STARTTLS works, but the MX certificate doesn't match the name. Matters for MTA-STS and DANE.

Yes, that is our own domain — the check found it.

Setup

Claude Code

claude mcp add --transport http runstack https://runstack.pro/api/mcp --header "X-RunStack-Key: rsk_..."

Cursor (`~/.cursor/mcp.json`) / VS Code / other clients

{
  "mcpServers": {
    "runstack": {
      "url": "https://runstack.pro/api/mcp",
      "headers": { "X-RunStack-Key": "rsk_..." }
    }
  }
}

Codex (`~/.codex/config.toml`)

[mcp_servers.runstack]
url = "https://runstack.pro/api/mcp"
http_headers = { "X-RunStack-Key" = "rsk_..." }

Language

Diagnoses are in English on runstack.pro. Russian: https://runstack.ru/api/mcp or ?lang=ru.

Reviews

No reviews yet

Be the first to review this server!

4.7

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.