Network Utilities

Private Ip Ranges

Returns the three RFC 1918 private IP address ranges in structured format. Access via MCP in Cursor or Windsurf for network configuration tasks, or hit GET /v1/network/private-ip-ranges directly. Returns Class A (10.0.0.0/8), Class B (172.16.0.0/12), and Class C (192.168.0.0/16) ranges with CIDR notation, subnet masks, and address counts—no guesswork needed.

API Endpoint

GET /v1/network/private-ip-ranges

Code Examples

curl "https://tinyfn.io/v1/network/private-ip-ranges" \
  -H "X-API-Key: YOUR_API_KEY"
const response = await fetch('https://tinyfn.io/v1/network/private-ip-ranges', {
  headers: { 'X-API-Key': 'YOUR_API_KEY' }
});
const data = await response.json();
console.log(data);
import requests

response = requests.get('https://tinyfn.io/v1/network/private-ip-ranges',
    headers={'X-API-Key': 'YOUR_API_KEY'})
data = response.json()
print(data)

Use via MCP

Add to your AI agent

Connect your AI agent (Claude, Cursor, Windsurf, etc.) to TinyFn's network tools:

{
  "mcpServers": {
    "tinyfn-network": {
      "url": "https://tinyfn.io/mcp/network",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Learn more about MCP setup →

FAQ

What are the RFC 1918 private IP ranges?

Class A: 10.0.0.0/8 (16.7M addresses), Class B: 172.16.0.0/12 (1M addresses), Class C: 192.168.0.0/16 (65K addresses). These ranges are reserved for private networks and not routable on the public Internet.

How do I use private IP ranges with MCP in Cursor?

Call the private-ip-ranges MCP tool to get structured data for network planning. Perfect for AI agents configuring subnets, validating IP assignments, or generating network documentation without hardcoding ranges.

What format does the private IP ranges API return?

Returns JSON with each range's CIDR notation, subnet mask, start/end addresses, and total address count. Includes both human-readable descriptions and machine-parseable network data.

Can I check if an IP address falls within private ranges?

This tool returns the ranges themselves—use TinyFn's IP validation tools to check if a specific address falls within these returned private ranges.

Why use an API for standard RFC 1918 ranges?

Eliminates hardcoding and typos in network automation scripts. AI agents get consistent, structured data instead of potentially hallucinating incorrect subnet masks or address counts.

Try Private Ip Ranges Now

Get your free API key and start using Private Ip Ranges in seconds.

Get Free API Key