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 分

    請在儲存庫或註冊中心條目中宣告授權條款。