# betterstack-mcp

Latency breakdown, response times and page audits - no API key.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** Unknown
- **License:** MIT
- **npm:** betterstack-mcp
- **Source:** https://github.com/mrfentmen/premium-mcps
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-19T19:17:43.721Z
- **Version scanned:** 1.0.2
- **CVEs:** none found by OSV at scan time

## Tools

13 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `response_times` — Sample a URL several times and report min, median, average, max and jitter, so you can tell steady from flaky.
- `latency_breakdown` — Split one request into DNS, TCP connect, TLS handshake and time-to-headers, and say which stage is slowest.
- `content_check` — Audit a page's title, meta description, canonical, lang, viewport, headings, image alt text and word count.
- `redirect_chain` — Every hop from the URL you give to the URL that finally answers, with timing and loop detection.
- `headers_report` — Grouped response headers — origin, caching and CDN, compression, security and cookies — with what looks wrong.
- `endpoint_summary` — One call for a whole endpoint: reachable or not, latency stages, TLS certificate age and DNS address.
- `certificate_info` — Read the TLS certificate a host presents: subject, issuer, validity and days left, chain length, SAN list and whether Node trusts it.
- `dns_records` — Look up a domain's A, AAAA, CNAME, MX, TXT, NS and CAA records at once and report its SPF and DMARC status.
- `port_check` — Test whether TCP ports accept a connection, with the time each port took and the reason a port is closed.
- `tls_versions` — Check whether a host still negotiates TLS 1.2 and TLS 1.3, and which protocol and cipher it picks for each.
- `domain_registration` — RDAP registration record for a domain: registrar, creation and expiry dates, registry locks, DNSSEC and nameservers.
- `host_network` — Where a host is served from: IP, autonomous system, operator, reverse DNS and city/country.
- `crawl_rules` — robots.txt directives that apply to a generic crawler, plus the sitemaps the site declares.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"betterstack\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"betterstack-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/betterstack-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/betterstack-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/betterstack-mcp
- HTML page: https://forgeregistry.com/registry/betterstack-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.