Give your AI agent real network diagnostics.
Connect toolhq to a compatible AI coding tool and let your agent inspect DNS, TLS, email and network infrastructure without leaving your workflow. No key, no account, one endpoint.
what your agent can do
These are the checks that need real network access, the thing a model cannot do on its own. Every one runs the same code as the tool on the site.
Read every DNS record for a domain, or one record type at a time.
DNS Lookup in the browserInspect a host’s TLS certificate: validity, issuer, SAN, chain, and expiry.
SSL Checker in the browserList a domain’s mail servers with priorities and resolved addresses.
MX Lookup in the browserTell whether an address is a VPN, proxy, Tor exit, or datacenter host.
VPN & Proxy Detector in the browserFetch a URL and report its status, redirect chain, and response headers.
HTTP Header Checker in the browserCompare a record across six public resolvers to see if a change has landed.
DNS Propagation Checker in the browserResolve PTR records for an address, with forward confirmation.
Reverse DNS (PTR Lookup) in the browserthings to ask for
- Check whether example.com has a valid SSL certificate.
- Verify the DNS records for example.com.
- Find the MX records for this domain.
- Inspect the HTTP response headers on this site.
- Check whether this IP has reverse DNS configured.
- Help me understand why email for this domain may not be working.
- Has my new A record propagated yet?
- Is this IP address a VPN or a datacenter host?
connect your client
Pick your agent and paste the configuration. The server speaks the MCP Streamable HTTP transport, so any client that supports a remote HTTP MCP server will work even if it is not listed here.
claude mcp add --transport http toolhq https://toolhq.io/api/mcp
privacy and limits
- A call sends one argument: a domain, host, IP address or URL. It is used to make the lookup and is not stored.
- No key, token or account. Nothing to sign up for and nothing to rotate.
- 60 requests per minute per IP address. Requests to private and internal addresses are refused.
- The endpoint is in beta. Tool names are stable; responses may gain fields as checks improve.
questions
Does toolhq MCP need an API key or an account?
No. The endpoint is open over HTTP and needs no key, token or account. Requests are rate limited by IP address.
Which checks are available to an agent?
8: dns_lookup, ssl_check, mx_lookup, ip_lookup, ip_reputation, http_headers, dns_propagation, reverse_dns. These are the checks that need real network access, which is exactly what a model cannot do on its own. The browser-only utilities such as the JSON formatter and JWT decoder are not exposed, because an agent can already do that work locally.
What does toolhq see when my agent runs a check?
The argument the agent sends: a domain, a host, an IP address or a URL. That value is used to make the lookup and is not stored. The same SSRF guards and rate limits as the website apply.
Is it stable?
The endpoint is in beta. The transport is the MCP Streamable HTTP transport and the tool names are stable, but new checks may be added and responses may gain fields.