Boilerplate MCP Server

Retrieve geolocation and network information for a public IP address. Returns TOON format by default (30-60% fewer tokens than JSON). **IMPORTANT - Cost Optimization:** - Use `jq` param to extract only needed fields. Unfiltered responses are expensive! - Example: `jq: "{ip: query, country: country, city: city}"` - extract specific fields - If unsure about available fields, first call WITHOUT jq filter to see all fields, then use jq in subsequent calls **Schema Discovery Pattern:** 1. First call: `ipAddress: "8.8.8.8"` (no jq) - explore available fields 2. Then use: `jq: "{ip: query, location: {city: city, country: country}}"` - extract only what you need **Output format:** TOON (default, token-efficient) or JSON (`outputFormat: "json"`) **Parameters:** - `ipAddress` - IP to lookup (omit for current device's public IP) - `includeExtendedData` - Include ASN, host, proxy detection (requires API token) - `useHttps` - Use HTTPS (default: true) - `jq` - JMESPath expression to filter response - `outputFormat` - "toon" (default) or "json" **JQ examples:** `query` (IP only), `{ip: query, country: country}`, `{location: {lat: lat, lon: lon}}` **Note:** Cannot lookup private IPs (192.168.x.x, 10.x.x.x). Powered by ip-api.com.

Retrieve IP address details and return both direct content and a resource link. **Consistency with ip_get_details:** - Uses the same arguments: `ipAddress`, `includeExtendedData`, `useHttps`, `jq`, `outputFormat` - Uses the same output rendering pipeline (TOON by default, JSON when `outputFormat: "json"`) **What this returns:** - A normal text response (same rendered output as `ip_get_details`) - A `resource_link` entry pointing to `ip://<resolved-ip>` for resource-style clients **Note:** Cannot lookup private IPs (192.168.x.x, 10.x.x.x). Powered by ip-api.com.

Generate a structured analysis request for IP address geolocation and network information

Lookup Google DNS server

Lookup Cloudflare DNS server