MCP & agents

NetTools is built to be used by AI agents, not just people. Its networked diagnostics are exposed over a remote MCP (Model Context Protocol) server, so an agent can check a domain, resolve DNS, or inspect a certificate as a tool call.

Connect

The MCP server speaks SSE. Point any MCP client at:

https://mcp.abr.cloud/mcp/sse

For example, in Claude Code's ~/.claude/mcp.json:

{
  "mcpServers": {
    "abr-nettools": {
      "type": "sse",
      "url": "https://mcp.abr.cloud/mcp/sse"
    }
  }
}

No account or API key is needed — the endpoint is free and unauthenticated for the safe single-target diagnostics.

Tools

Every tool takes a single target (a domain, host, or IP). The star is domainhealth, which returns a full graded snapshot (TLS, HTTPS redirect, SPF, DMARC, DNSSEC, MX, blacklist) in one call — a good default for "is this domain healthy?". Also available: dns, spf, dmarc, mx, caa, dnssec, certexpiry, tlscheck, certview, http, redirects, ipgeo, asn, ping, traceroute, and more.

The full machine-readable catalogue lives at nettools.abr.cloud/llms-full.txt; the short version + this endpoint are at /llms.txt.

Discovery

For agents that discover capabilities automatically, we publish:

• /.well-known/api-catalog (RFC 9727) — links to the MCP endpoint and docs.
• /.well-known/mcp/server-card.json — the MCP server card.
• /.well-known/agent-skills/index.json — a skills index (e.g. a one-call domain health check).
• Link headers (RFC 8288) on the homepage pointing at the catalog.

Limits & fair use

The endpoint is rate-limited per IP and exposes only the safe, single-target lookups — the active scanners are deliberately not available here. Heavy or abusive use is throttled. If you need higher volume or the full toolset programmatically, get in touch: [email protected].