# RunStack Checks

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

- name: pro.runstack/checks
- version: 1.0.1
- connection class: R1 (autonomous)
- trust: 96/100
- quality: 89/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/pro.runstack%2Fchecks
- tools: https://api.protogrid.dev/v1/servers/pro.runstack%2Fchecks/tools

**An agent can connect on its own if it already holds `X_RUNSTACK_KEY`, `X_RUNSTACK_KEY`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "checks": {
      "type": "http",
      "url": "https://runstack.pro/api/mcp",
      "headers": {
        "X-RunStack-Key": "${X_RUNSTACK_KEY}",
        "Authorization": "${X_RUNSTACK_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_RUNSTACK_KEY}`, `${X_RUNSTACK_KEY}`.

## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-2d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,272 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 2 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 1,272 tokens to load them all
- tool set hash: f8f69f5b620fc191f2e495c0fb138da3
- tools last changed: 2026-10-18T11:03:31.551Z
- badge: [![protogrid quality](https://protogrid.dev/badge/pro.runstack/checks.svg)](https://protogrid.dev/servers/pro.runstack/checks)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-18 `ip_lookup` removed
  - 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 to check PTR/RPKI for a mail or BGP issue.
- 2026-10-18 `check_ip` added
  - 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).
- 2026-10-18 `check_port` changed (description, inputSchema, outputSchema, annotations)
  - before: Check from the internet whether TCP ports of a public host are open, closed or filtered. Use to verify firewall / security group rules, or why a service is reachable locally but not from outside. Only public addresses are allowed.
  - after: 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).
- 2026-10-18 `check_dns` changed (description, inputSchema, outputSchema, annotations)
  - before: Resolve a name at several public resolvers (Google, Cloudflare, Quad9, …) and compare answers. Use after changing DNS records to check propagation, or when some users reach a different IP or get NXDOMAIN. Returns per-resolver answers and inconsistencies.
  - after: 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.
- 2026-10-18 `check_email_domain` changed (description, inputSchema, outputSchema, annotations)
  - before: Audit a mail domain as other mail servers see it: MX, SPF (with 10-lookup count), DKIM, DMARC, PTR/FCrDNS, SMTP STARTTLS, MTA-STS, TLS-RPT, BIMI. Use when mail lands in spam or bounces, after changing mail provider or DNS, or before tightening DMARC. Returns a verdict, findings with cause and fix, and a report link.
  - after: 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.
- 2026-10-18 `check_http` changed (description, inputSchema, outputSchema, annotations)
  - before: Fetch a public URL from outside your network: status, redirect chain, TLS, security headers (HSTS, CSP, X-Frame-Options…), caching and compression. Use to debug redirect loops, wrong status codes or missing headers as real visitors and CDNs see them, or to verify a web server config change after deploy. Returns a verdict and findings with fixes.
  - after: 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.
- 2026-10-18 `check_tls` changed (description, inputSchema, outputSchema, annotations)
  - before: Scan a public host's TLS from the internet: certificate validity and chain, expiry, hostname match, protocols (TLS 1.0–1.3), ciphers, HSTS. Use when a site shows certificate errors, before/after renewing or rotating a certificate, or to confirm old TLS versions are off. Returns a verdict, findings with cause and fix, and a shareable report link. Takes up to ~60 s.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/pro.runstack%2Fchecks/changes

## Remotes

- https://runstack.pro/api/mcp (streamable-http, auth api_key ${X_RUNSTACK_KEY}, reachable true, uptime30d 1)

## Packages

_none_

## Tools (6)

- `check_dns`: 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.
- `check_email_domain`: 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.
- `check_http`: 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.
- `check_ip`: 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).
- `check_port`: 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).
- `check_tls`: 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.