`rdap_ip`

Pack: rdap · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/rdap_ip for the schema, then POST the same URL with its arguments for the data.

WHICH COMPANY OWNS THIS IP — the one tool to call for “who owns ”, “what network is in”, “ASN / network range / owner of ”. Returns an owner block with ASN, owner name, network range (announced prefix and registry allocation) and owner domain, each stating its source (RIR registration data via RDAP, RIPE NCC routing data, PeeringDB); a field no source states is null with a reason, never guessed. Also returns the registry’s full RDAP record (allocation, registrant, abuse contact) as rdap. Keyless; fails over between the registry’s endpoints when one refuses the connection.

Parameters

Name	Type	Required	Description
`address`	string	no	IP address, e.g. “8.8.8.8”. Also accepted as `ip`.
`ip`	string	no	Alias for `address`.

Example call

Arguments

{
  "address": "8.8.8.8"
}

curl

curl -X POST https://gateway.pipeworx.io/rdap/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"rdap_ip","arguments":{"address":"8.8.8.8"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('rdap_ip', {
  "address": "8.8.8.8"
});

More examples

{
  "address": "192.0.2.0/24"
}

Response shape

Full JSON Schema

{
  "type": "object",
  "description": "RDAP IP/netblock allocation record"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the rdap pack

{
  "mcpServers": {
    "rdap": {
      "url": "https://gateway.pipeworx.io/rdap/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

rdap_ip