- What it does
- Check whether an IP address falls inside each CIDR range you send, IPv4 or IPv6, with the network, netmask, broadcast, usable range and address counts, the most specific match, and a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
cidr_containsat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
CIDR Contains Check (IPv4 and IPv6) is for coding and operations agents that write or debug allow lists, firewall rules, security groups and subnets and need the same exact containment answer and address counts every time. Check whether an IP address falls inside each CIDR range you send (allow lists, firewall rules, security groups, VPC subnets). Send one IPv4 or IPv6 address and up to 100 ranges such as 10.0.0.0/8 or 2001:db8::/32. Get back, per range: inside or not, the network, the netmask (IPv4), the broadcast address (IPv4), the first and last usable address, the total and usable address counts, and a flag when the range was written with host bits set (10.0.0.5/24 means 10.0.0.0/24); plus every range that matches and the most specific one (longest prefix). IPv4 /31 and /32 are handled the way RFC 3021 and routers do; IPv6 has no broadcast address. It is one of the developer department tools LLPRO builds for the work agents do across business software (Aws, Cloudflare, GitHub). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Coding and operations agents that write or debug allow lists, firewall rules, security groups and subnets and need the same exact containment answer and address counts every time.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, cidrs up to 100 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not look anything up: no DNS, no WHOIS, no cloud provider ranges, no reachability. Does not say whether an address is private, reserved or routable on the internet, does not merge or compare ranges with each other, and does not read firewall rule order or deny rules: inside a range is not the same as allowed. Zone IDs (fe80::1%eth0) and ports are refused; send the bare address. An IP address can point to a person's connection: it is checked, never stored.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "cidr_contains", "arguments": {"ip": "192.168.1.130", "cidrs": ["192.168.1.0/24", "192.168.1.128/25", "10.0.0.0/8"]}}}For agents
Tool cidr_contains on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:uuhy5l5mcug5g2ve5s6rymf75u): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): x6T4P4lCBIBDWWwpkpSeuV39NdhYEEFce0d0u4639sY=
For agents that search MCP registries for CIDR, IP in range, subnet calculator tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: A CIDR check is one step of setting up or debugging network access. Tell LLPRO the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card