TCPLab Network Tools

npx add-mcp 'https://tcp.lc/mcp'

A public MCP server over Streamable HTTP. Any MCP-capable client can add it as a tool source and run the same network lookups as the web tools. No API key or token is required.

Connect

Add the endpoint to your MCP client configuration:

{
  "mcpServers": {
    "tcplab": { "type": "http", "url": "https://tcp.lc/mcp" }
  }
}

The endpoint is stateless: no session id is issued, and any instance can serve any request.

Auto-approve

Whether a tool call needs confirmation is decided by your MCP client, not by this server — so this is configured on the client side. Some clients read an autoApprove field on the server entry; its shape differs per client.

Cline uses an array of tool names. Wildcards are not supported, so list them explicitly:

{
  "mcpServers": {
    "tcplab": {
      "type": "http",
      "url": "https://tcp.lc/mcp",
      "autoApprove": [
        "ip_lookup", "my_ip", "dns_query", "dns_domain_ready",
        "whois_lookup", "http_check", "tls_check", "domain_report"
      ]
    }
  }
}

Cursor reads "autoApprove": true on the entry, but it also needs Auto-Run Mode enabled in Settings → Agents. A wildcard does not work there: wildcard allowlist entries are ignored and only exact tool names apply.

Claude Code instead uses a permission rule in settings.json, for example "permissions": { "allow": ["mcp__tcplab"] } for every tool, or mcp__tcplab__ip_lookup for one. Other clients expose a per-tool "Always allow" toggle in their UI.

Every tool here is marked read-only (readOnlyHint: true), which some clients use as a signal to prompt less.

Tools

Tool	Parameters	Description
ip_lookup	target, lang?	Geolocation of an IPv4/IPv6 address or domain (a domain is resolved first).
my_ip	lang?	Geolocation of the calling client's own IP.
dns_query	name, type?, server?	Query A, AAAA, CNAME, TXT, MX or NS records.
dns_domain_ready	name, server?	Both A and AAAA records in one call.
whois_lookup	domain	Registrar, dates, statuses and nameservers over RDAP/WHOIS.
http_check	url	HTTP status, response headers and the IP/HTTP version used.
tls_check	host, port?	Certificate detail (subject, issuer, validity, SAN), TLS version and HTTP/2 support.
domain_report	domain, locale?, refresh?	Comprehensive health report with a 0-100 score and grade. Slow on first generation; cached afterwards.

Each tool returns a readable text summary plus structured content with the full result.

General

• The tools call the same backend as the JSON API, so results, caching and error messages match.
• Arguments are normalized by the server: http_check assumes https:// when the scheme is missing, and tls_check defaults to port 443.
• domain_report is the slowest tool: DNS/WHOIS/TLS/HTTP probing plus an optional AI summary, worst case around 50 seconds on a cache miss. Give your MCP client a timeout of at least 60 seconds.

Rate limits

Limits are per client IP and identical to the JSON API; every tool call counts. MCP clients that share an egress IP (for example a hosted assistant) also share the quota. When a limit is exceeded the tool returns an error message explaining when to retry.