betterstack-mcp

MCPcommunity
v1.0.2UnknownMITUpdated 3d agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
10Downloads/wk
3d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.0.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface13 tools · none privileged
Security scan✓ Cleanv1.0.2 · todayHow well does this scan work?
EvalsNone
IndexedOct 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

13 tools · none privileged
Statically extracted from the published packagev1.0.2 · 10h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

response_timesSample a URL several times and report min, median, average, max and jitter, so you can tell steady from flaky.

Sample a URL several times and report min, median, average, max and jitter, so you can tell steady from flaky.

No input schema was published for this tool.

latency_breakdownSplit one request into DNS, TCP connect, TLS handshake and time-to-headers, and say which stage is slowest.

Split one request into DNS, TCP connect, TLS handshake and time-to-headers, and say which stage is slowest.

No input schema was published for this tool.

content_checkAudit a page's title, meta description, canonical, lang, viewport, headings, image alt text and word count.

Audit a page's title, meta description, canonical, lang, viewport, headings, image alt text and word count.

No input schema was published for this tool.

redirect_chainEvery hop from the URL you give to the URL that finally answers, with timing and loop detection.

Every hop from the URL you give to the URL that finally answers, with timing and loop detection.

No input schema was published for this tool.

headers_reportGrouped response headers — origin, caching and CDN, compression, security and cookies — with what looks wrong.

Grouped response headers — origin, caching and CDN, compression, security and cookies — with what looks wrong.

No input schema was published for this tool.

endpoint_summaryOne call for a whole endpoint: reachable or not, latency stages, TLS certificate age and DNS address.

One call for a whole endpoint: reachable or not, latency stages, TLS certificate age and DNS address.

No input schema was published for this tool.

certificate_infoRead the TLS certificate a host presents: subject, issuer, validity and days left, chain length, SAN list and whether Node trusts it.

Read the TLS certificate a host presents: subject, issuer, validity and days left, chain length, SAN list and whether Node trusts it.

No input schema was published for this tool.

dns_recordsLook up a domain's A, AAAA, CNAME, MX, TXT, NS and CAA records at once and report its SPF and DMARC status.

Look up a domain's A, AAAA, CNAME, MX, TXT, NS and CAA records at once and report its SPF and DMARC status.

No input schema was published for this tool.

port_checkTest whether TCP ports accept a connection, with the time each port took and the reason a port is closed.

Test whether TCP ports accept a connection, with the time each port took and the reason a port is closed.

No input schema was published for this tool.

tls_versionsCheck whether a host still negotiates TLS 1.2 and TLS 1.3, and which protocol and cipher it picks for each.

Check whether a host still negotiates TLS 1.2 and TLS 1.3, and which protocol and cipher it picks for each.

No input schema was published for this tool.

domain_registrationRDAP registration record for a domain: registrar, creation and expiry dates, registry locks, DNSSEC and nameservers.

RDAP registration record for a domain: registrar, creation and expiry dates, registry locks, DNSSEC and nameservers.

No input schema was published for this tool.

host_networkWhere a host is served from: IP, autonomous system, operator, reverse DNS and city/country.

Where a host is served from: IP, autonomous system, operator, reverse DNS and city/country.

No input schema was published for this tool.

crawl_rulesrobots.txt directives that apply to a generic crawler, plus the sitemaps the site declares.

robots.txt directives that apply to a generic crawler, plus the sitemaps the site declares.

No input schema was published for this tool.

13 of 13 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
observabilitylatencyperformanceseoheadersmcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-19 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in monitoring & logging