Integration

ipbase integration

ipbase resolves IP addresses to geolocation (country, region, city, coordinates, timezone), network owner (ASN, ISP, organization), security signals (VPN, proxy, Tor, datacenter, bot, threat score) and the domains hosted on an address. Look up one address or up to 1,000 in one batch, look up an autonomous system number, list the domains hosted on an IPv4 address, and read the account's remaining monthly quota. The query-string variant of the batch lookup is not exposed (the batch tool covers it). Authentication is an API key sent in the apikey header; a free key is accepted by every endpoint, but the ASN and hosted-domain lookups answer only on a plan that includes them.

Connect ipbase How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in ipbase.Built from the 5 ipbase tools below, on the connection you add once.

What you can do with ipbase

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Ip address, 2 operations

lookup_ipLookup ipGETLooks up one IPv4 or IPv6 address: geolocation, timezone, ASN and ISP, security flags (VPN, proxy, Tor, datacenter, bot, threat score) and hosted domains. Always pass ip: left out, the address looked up is the LiveContext server's own.
lookup_ips_batchLookup ips batchPOSTLooks up 1 to 1,000 IPv4 or IPv6 addresses in one call (needs an API key, the free one too) and returns, keyed by address, the same object lookup_ip returns. Each valid address costs one request of quota; invalid items go to errors.

Account, 1 operation

get_account_statusGet account statusGETReturns the account's quota usage (monthly and grace buckets: total, used, remaining) and its plan, plus when each data layer was last built. Does not count against the quota or rate limit.

Asn, 1 operation

lookup_asnLookup asnGETLooks up an autonomous system number: its organization, ISP, country, domain and announced IP ranges. Needs a plan that includes the ASN endpoint; paid plans also get its class, registry, peers, upstreams, downstreams and RPKI states.

Hosted domain, 1 operation

list_hosted_domainsList hosted domainsGETLists the domains hosted on an IPv4 address (from A records), with the total count. Cursor-paginated: pass next_cursor back as cursor for the next page. Needs a plan that includes the hosted domains endpoint.

Use ipbase from Claude Code, Cursor or Codex

Connect ipbase in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ipbase operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect ipbase

Create your workspace
Sign up free. Nothing to install.
Connect ipbase once
Add your ipbase connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.