RunStack Checks
REMOTE · RUNSTACK.PRO
External checks of TLS, HTTP, email domain, DNS, ports, blocklists and domain expiry
Available components
Last scanned (4 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1267 tokens (~158/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management45
- Stability check failed: schema churn in the 19 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 38 to 41.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 31 to 35.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 25 to 28.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 11 to 15.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 1 to 5.
- 20 Oct 26 0
- Schema quality: 957 → 1267 ▼ functional
- New tool “check_dnsbl” functional
- New tool “check_domain_expiry” functional
- 19 Oct 26 −1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “ip_lookup” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_dns” rewrote its description, which is the text the model reads security
- Tool “check_email_domain” rewrote its description, which is the text the model reads security
- Tool “check_http” rewrote its description, which is the text the model reads security
- Tool “check_port” rewrote its description, which is the text the model reads security
- Tool “check_tls” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool “check_dns” now declares an output schema ▲ functional
- Tool “check_email_domain” now declares an output schema ▲ functional
- Tool “check_http” now declares an output schema ▲ functional
- Tool “check_port” now declares an output schema ▲ functional
- Tool “check_tls” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- New tool “check_ip” functional
- “check_dns” reworded the description of “domain” cosmetic
- “check_dns” reworded the description of “type” cosmetic
- “check_email_domain” reworded the description of “dkimSelector” cosmetic
- “check_email_domain” reworded the description of “domain” cosmetic
- “check_http” reworded the description of “followRedirects” cosmetic
- “check_http” reworded the description of “url” cosmetic
- “check_port” reworded the description of “host” cosmetic
- “check_port” reworded the description of “ports” cosmetic
- “check_tls” reworded the description of “host” cosmetic
- “check_tls” reworded the description of “port” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://runstack.pro/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=runstack.pro | CN=YE1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d61a224cb70ec95d40be07497661740857 |
| SANs: runstack.pro, www.runstack.pro | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of runstack.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 33289 | 8 | Verified |
| runstack.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' https://yoomoney.ru; script-src 'self' 'unsafe-inline' https://smartcaptcha.yandexcloud.net https://mc.yandex.ru https://mc.yandex.com https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; frame-src https://smartcaptcha.yandexcloud.net https://*.captcha.yandex.net https://mc.yandex.ru https://mc.yandex.com; connect-src 'self' https://smartcaptcha.yandexcloud.net https://smartcaptcha.cloud.yandex.ru https://mc.yandex.ru https://mc.yandex.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; worker-src 'self' blob:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://runstack.pro/api/mcp | Verified | 200 | |
| http (plaintext) | http://runstack.pro/api/mcp | HTTPS enforced | 301 | https://runstack.pro/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_dns DNS lookup across resolvers ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or hostname to resolve, e.g. www.example.com |
| type | string | – | Record type to query. ALL queries the common types at once. Default ALL. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_dnsbl DNSBL / blocklist check ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Public IPv4/IPv6 address of the sending mail server, or a domain, e.g. 203.0.113.10 or example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_domain_expiry Domain registration / expiry ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. example.com or пример.рф |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_email_domain Email domain check ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dkimSelector | string | – | DKIM selector to check in addition to common ones, e.g. google, selector1, mail. Optional. |
| domain | string | yes | Mail domain (the part after @), e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_http HTTP response inspection ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| followRedirects | boolean | – | Follow redirects and report every hop (default true). Set false to see only the first response. |
| url | string | yes | Full public http(s) URL, e.g. https://example.com/login |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_ip IP / ASN lookup ~118
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).
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | IPv4 or IPv6 address, or an ASN, e.g. 1.1.1.1, 2606:4700::1111 or AS13335 |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_port Port reachability from the internet ~124
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).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Public hostname or IP address, e.g. example.com or 203.0.113.10 |
| ports | string | yes | Comma-separated TCP ports, e.g. 22,80,443 |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
check_tls TLS / certificate check ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Public hostname to scan, without scheme or path, e.g. example.com |
| port | integer | – | TLS port, e.g. 443 (HTTPS), 465 (SMTPS), 993 (IMAPS). Default 443. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Error code when ok is false |
| facts | array | – | – |
| findings | array | – | – |
| headline | string | – | One-line summary |
| message | string | – | – |
| notice | string | – | Usage note, e.g. anonymous-tier limits |
| ok | boolean | yes | false when the check could not run (see error / message) |
| reportUrl | string | – | Shareable report link |
| target | string | – | What was checked |
| tool | string | – | – |
| verdict | string | – | – |
No examples provided.
How do I install the RunStack Checks MCP server?
RunStack Checks is a hosted endpoint at https://runstack.pro/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · runstack.pro
claude mcp add --transport http pro-runstack-checks 'https://runstack.pro/api/mcp'
What is the RunStack Checks MCP server?
RunStack Checks is an MCP server listed in the public MCP registry as pro.runstack/checks. External checks of TLS, HTTP, email domain, DNS, ports, blocklists and domain expiry. This page covers its hosted endpoint (https://runstack.pro/api/mcp).
Is the RunStack Checks MCP server safe to use?
RunStack Checks scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RunStack Checks MCP server expose?
RunStack Checks exposes 8 tools: check_tls, check_http, check_email_domain, check_dns, check_port, and 3 more. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.
Does the RunStack Checks MCP server require authentication?
No. We connected to RunStack Checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RunStack Checks MCP server still maintained?
RunStack Checks is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.