RunStack Checks

pro.runstack由 runstack.pro 发布官方发布者v1.0.2更新于 Nov 1, 2026

External checks of TLS, HTTP, email domain, DNS, ports, blocklists and domain expiry

已验证Streamable HTTP可网页运行云端与基础设施安全与监控

概览

AI 生成的概览

远程 MCP 服务器,从外部检查公网 TLS、HTTP、DNS、邮件、端口、黑名单和域名到期情况,并给出诊断结论。

可以做什么
  • 检查公网主机的 TLS 证书、证书链、协议版本、加密套件与 HSTS
  • 检查 HTTP 状态码、重定向链、安全响应头、缓存与压缩
  • 审计邮件域名:MX、SPF、DKIM、DMARC、PTR、STARTTLS、MTA-STS、TLS-RPT、BIMI
  • 对比多个公共解析器的 DNS 结果,并从公网检测 TCP 端口
  • 查询 IP/ASN 归属、PTR、RPKI 与地理位置,检查 DNSBL/RBL 黑名单
  • 查询域名注册信息、到期时间、EPP 状态、域名服务器与 DNSSEC
适用场景
适合排查证书报错、重定向循环、缺失的安全响应头、邮件进垃圾箱、修改 DNS 记录后的传播、防火墙规则、黑名单收录或域名即将到期等问题,且关注的是用户和其他邮件服务器实际看到的结果,而非本机网络视角。
运行要求
远程 Streamable HTTP 端点,无需本地运行。可选免费 API 密钥通过 X-RunStack-Key 请求头(或 Bearer 令牌)发送,可将额度提升至每天 200 次;不提供密钥时每个 IP 每天 10 次。需要能访问该端点的网络。
安装前请注意
API 密钥属于机密,需通过请求头发送,避免写入共享配置。仅支持公网主机和地址,因此提交的主机名与 IP 会发送给第三方服务。工具均声明为只读,但结果中会包含服务商网站上的报告链接。

安装

在 SourceWeft 中

  1. 打开 控制台中的 RunStack Checks,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/pro.runstack%2Fchecks/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

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

ToolWhat it checks
check_tlsCertificate validity and chain, expiry, hostname, TLS 1.0–1.3, ciphers, HSTS
check_httpStatus, redirect chain, security headers (HSTS, CSP, X-Frame-Options…), caching, compression
check_email_domainMX, SPF (10-lookup limit), DKIM, DMARC, PTR/FCrDNS, STARTTLS, MTA-STS, TLS-RPT, BIMI
check_dnsAnswers from several public resolvers compared — propagation, NXDOMAIN, inconsistencies
check_portTCP ports open / closed / filtered from the internet
check_ipIP 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

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

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

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

Codex (~/.codex/config.toml)

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.

Links

来源:README.md,提交 eb3a317

工具

8

check_tls

TLS / certificate check

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.

输入参数host必填port

check_http

HTTP response inspection

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.

输入参数url必填followRedirects

check_email_domain

Email domain check

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.

输入参数domain必填dkimSelector

check_dns

DNS lookup across resolvers

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.

输入参数typedomain必填

check_port

Port reachability from the internet

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).

输入参数host必填ports必填

check_ip

IP / ASN lookup

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).

输入参数input必填

check_dnsbl

DNSBL / blocklist check

Check whether an IP address or a domain is on email blocklists (DNSBL/RBL): Spamhaus ZEN and DBL, SpamCop, Barracuda, UCEPROTECT, Mailspike, SURBL, URIBL and others. For a domain, its own name is checked on domain lists and its A/AAAA addresses on IP lists. Use when mail bounces with 'listed'/'blocked' errors or lands in spam, or after a server was compromised. Lists that refuse queries from public resolvers are reported as not tested, never as listed. Returns listed lists with the reason and a delisting link. For SPF/DKIM/DMARC use check_email_domain.

输入参数input必填

check_domain_expiry

Domain registration / expiry

Look up a domain's registration in the registry (RDAP, or WHOIS for .ru/.su/.рф): expiry date and days left, registrar, creation date, EPP status codes (clientHold, redemptionPeriod, transfer locks…) with explanations, nameservers and DNSSEC. Use to check when a domain must be renewed or why it suddenly stopped resolving. Subdomains are reduced to the registered domain. For DNS records use check_dns.

输入参数domain必填

版本历史

2
  1. v1.0.2最新Nov 1, 2026
  2. v1.0.1Oct 17, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。