RunStack Checks MCP server
Commit Oct 18, 2026Performs external infrastructure audits for TLS, HTTP, email domains, DNS, ports, and IP configurations to provide diagnostic reports.
Also known as WithoutCowards/runstack-mcp, runstack-mcp
- Stars
- 0
- Tools
- 6
- Downloads, 30 days
- —
- Latest version
- 1.0.2
- Last commit
- Oct 18, 2026
- License
- —
What is RunStack Checks MCP?
RunStack Checks performs external infrastructure audits for TLS, HTTP, email domains, DNS, ports, and IP configurations to provide diagnostic reports. It exposes 6 tools, such as check_tls, check_http, check_email_domain.
Summary generated from the project's README
About RunStack Checks MCP server
RunStack Checks provides a remote MCP server designed for AI agents to perform external infrastructure audits. It examines public data from an outside perspective, simulating how browsers, users, and mail servers interact with a domain. This server operates via a stateless HTTP endpoint and requires an API key provided through an X-RunStack-Key or Bearer token header. A free tier allows for 200 calls per day.
Developers can use specific tools to diagnose various network components. The check_tls tool verifies certificate validity and HSTS, while check_http examines security headers and redirect chains. For email configuration, check_email_domain audits MX, SPF, DKIM, and DMARC records. Other capabilities include check_dns for propagation consistency, check_port for TCP port status, and check_ip for ASN and geolocation data. Every diagnostic result includes a verdict, the cause of any issues, and suggested fixes.
What you can do with it
- 1Audit email security configurationsAsk the AI to verify if a domain has valid SPF, DKIM, and DMARC records to prevent mail delivery issues.
Written from the project's README. Every use case is checked against a quote from it.
How to install RunStack Checks MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall RunStack Checks MCP in Claude Code
$ claude mcp add --transport http runstack-mcp https://runstack.pro/api/mcpInstall RunStack Checks MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"runstack-mcp": {
"url": "https://runstack.pro/api/mcp"
}
}
}Install RunStack Checks MCP in VS Code
.vscode/mcp.json
{
"servers": {
"runstack-mcp": {
"type": "http",
"url": "https://runstack.pro/api/mcp"
}
}
}Install RunStack Checks MCP in VS Code CLI
$ code --add-mcp '{"name":"runstack-mcp","type":"http","url":"https://runstack.pro/api/mcp"}'Install RunStack Checks MCP in Codex
$ codex mcp add runstack-mcp --url https://runstack.pro/api/mcpInstall RunStack Checks MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.runstack-mcp] url = "https://runstack.pro/api/mcp"
Install RunStack Checks MCP in Gemini CLI
$ gemini mcp add -s user --transport http runstack-mcp https://runstack.pro/api/mcpInstall RunStack Checks MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"runstack-mcp": {
"url": "https://runstack.pro/api/mcp",
"type": "http"
}
}
}RunStack Checks MCP tools 6
Detected from the READMEcheck_tlscheck_httpcheck_email_domaincheck_dnscheck_portcheck_ip
| check_tls | — | |
| check_http | — | |
| check_email_domain | — | |
| check_dns | — | |
| check_port | — | |
| check_ip | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablewithoutcowards/runstack-mcp is public and reachablegithub.com/withoutcowards/runstack-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-01github.com/withoutcowards/runstack-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 1054 msPass
README
View on GitHubRunStack 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_...(orAuthorization: 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.
Links
- Website: https://runstack.pro
- REST API: https://runstack.pro/developers
- Telegram bot: https://t.me/RunStackru_bot
RunStack Checks MCP questions
How do I add RunStack Checks MCP to Claude Code?
Run claude mcp add --transport http runstack-mcp https://runstack.pro/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add RunStack Checks MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does RunStack Checks MCP provide?
It exposes 6 tools, including check_tls, check_http, check_email_domain, check_dns, check_port.
Does this server require local installation or access to my servers?
No, nothing runs locally or on your servers; it only checks public data from the outside.
Is there a free tier available?
Yes, you can get a free key that allows for 200 calls per day.