Service rollup, ports, DNS propagation and TLS chains - no API key.
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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.
status_summaryThe rollup a status page shows: how many services are up, which are down, the slowest one and the overall state.The rollup a status page shows: how many services are up, which are down, the slowest one and the overall state.
No input schema was published for this tool.
check_servicesUp/down sweep of up to 10 services in one call, with status code and response time for each.Up/down sweep of up to 10 services in one call, with status code and response time for each.
No input schema was published for this tool.
service_statusDetail for one service: HTTP status, response time, server, redirect chain and the first text on the page.Detail for one service: HTTP status, response time, server, redirect chain and the first text on the page.
No input schema was published for this tool.
port_checkCheck whether TCP ports on a host accept connections, with the service usually found on each port.Check whether TCP ports on a host accept connections, with the service usually found on each port.
No input schema was published for this tool.
dns_propagationAsk Cloudflare, Google and AdGuard for the same record and report whether they agree, plus the lowest TTL.Ask Cloudflare, Google and AdGuard for the same record and report whether they agree, plus the lowest TTL.
No input schema was published for this tool.
ssl_chainThe whole certificate chain from the live handshake: leaf, intermediates, expiry and whether the chain is trusted.The whole certificate chain from the live handshake: leaf, intermediates, expiry and whether the chain is trusted.
No input schema was published for this tool.
header_auditFetch a URL and report every response header it returned, with the security-relevant ones marked present or absent and what each one is for, so a missing HSTS or content security policy is visible. An optional path audits a different route on the same host, since headers are often set per route. Th…Fetch a URL and report every response header it returned, with the security-relevant ones marked present or absent and what each one is for, so a missing HSTS or content security policy is visible. An optional path audits a different route on the same host, since headers are often set per route. Th…
No input schema was published for this tool.
dns_recordsRead the DNS record types the existing propagation tool never asks for: AAAA, MX, TXT, NS, CNAME, SOA and CAA alongside A. Every type is asked of two resolvers over DoH and compared, so a record still in flight shows as a disagreement between them rather than as a single answer. The existing DNS to…Read the DNS record types the existing propagation tool never asks for: AAAA, MX, TXT, NS, CNAME, SOA and CAA alongside A. Every type is asked of two resolvers over DoH and compared, so a record still in flight shows as a disagreement between them rather than as a single answer. The existing DNS to…
No input schema was published for this tool.
cert_forecastJudge a host's certificate by what it leaves you rather than by the chain alone: how many days of validity remain and how many the term has in total, the key size and curve, whether the subject alternative names actually cover the hostname you asked about, whether the chain is trusted, the handshak…Judge a host's certificate by what it leaves you rather than by the chain alone: how many days of validity remain and how many the term has in total, the key size and curve, whether the subject alternative names actually cover the hostname you asked about, whether the chain is trusted, the handshak…
No input schema was published for this tool.
9 of 9 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.
Service rollup, ports, DNS propagation and TLS chains - no API key.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
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)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 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.