@pipeworx/ipify

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/ipify’s. Install: one-click buttons

Connect to just the @pipeworx/ipify pack

https://gateway.pipeworx.io/ipify/mcp — only @pipeworx/ipify’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 2

ipify MCP — keyless “what is my public IP” echo.

Tools

  • ipv4() — caller’s IPv4 (as gateway sees it — note: this is the CF Worker egress IP, not the upstream caller)
  • ipv6() — caller’s IPv6

When called via the pipeworx gateway, the returned IP is the Cloudflare egress IP that fetched the upstream — not the LLM/agent IP. Useful for verifying egress IPs / smoke tests.

Data source

https://api.ipify.org, https://api64.ipify.org

Tools

  • ipv4 — Caller’s IPv4 (gateway egress IP).
  • ipv6 — Caller’s IPv6 (gateway egress IP, IPv4 fallback).

Tools

  • ipv4 — Caller's IPv4 (gateway egress IP).
  • ipv6 — Caller's IPv6 (gateway egress IP, IPv4 fallback).

Regenerated from source · build October 2, 2026