RunStack Checks

pro.runstack

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

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "pro.runstack-checks": {4      "url": "https://runstack.pro/api/mcp",5      "headers": {}6    }7  }8}

.cursor/mcp.jsonMCP server

Transport: http
Status: Remote

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://runstack.pro/api/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

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

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "pro.runstack-checks": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://runstack.pro/api/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.1
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install RunStack Checks?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does RunStack Checks need an API key?

No required environment variable is listed on this record.

What transport does RunStack Checks use?

RunStack Checks is reached over HTTP.

When was RunStack Checks last checked?

Last checked 2026-10-28. External checks of TLS, HTTP headers, email domain, DNS and ports, with cause and fix

From the publisher

Documentation

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.

RunStack Checks

pro.runstack

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

Communication

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

GitHub Website

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "pro.runstack-checks": {4      "url": "https://runstack.pro/api/mcp",5      "headers": {}6    }7  }8}

.cursor/mcp.jsonMCP server

Transport: http
Status: Remote

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://runstack.pro/api/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

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

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "pro.runstack-checks": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://runstack.pro/api/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.1
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install RunStack Checks?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does RunStack Checks need an API key?

No required environment variable is listed on this record.

What transport does RunStack Checks use?

RunStack Checks is reached over HTTP.

When was RunStack Checks last checked?

Last checked 2026-10-28. External checks of TLS, HTTP headers, email domain, DNS and ports, with cause and fix

From the publisher

Documentation

RunStack MCP — external infrastructure checks for AI agents

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.

RunStack Checks

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install RunStack Checks?

Does RunStack Checks need an API key?

What transport does RunStack Checks use?

When was RunStack Checks last checked?

Documentation

RunStack MCP — external infrastructure checks for AI agents

Tools

Example (abridged, real output)

Setup

Claude Code

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

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

Language

Links

RunStack Checks

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install RunStack Checks?

Does RunStack Checks need an API key?

What transport does RunStack Checks use?

When was RunStack Checks last checked?

Documentation

RunStack MCP — external infrastructure checks for AI agents

Tools

Example (abridged, real output)

Setup

Claude Code

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

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

Language

Links

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install RunStack Checks?

Does RunStack Checks need an API key?

What transport does RunStack Checks use?

When was RunStack Checks last checked?

Documentation

RunStack MCP — external infrastructure checks for AI agents

Tools

Example (abridged, real output)

Setup

Claude Code

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

Codex (~/.codex/config.toml)

Language

Links

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install RunStack Checks?

Does RunStack Checks need an API key?

What transport does RunStack Checks use?

When was RunStack Checks last checked?

Documentation

RunStack MCP — external infrastructure checks for AI agents

Tools

Example (abridged, real output)

Setup

Claude Code

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

Codex (~/.codex/config.toml)

Language

Links

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

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

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

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