IP Intelligence Grounding Data

Overview

IP Lookup works by querying the IP address against a geolocation database and returning structured location data — country, region, city, coordinates, postal code, timezone and continent — plus the coordinate accuracy radius and whether the country is in the European Union.

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as IPIntelligenceGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "IPIntelligenceGroundingData",
  "arguments": {
    "ip": "173.172.81.20"
  }
}

You do not name the tool yourself; the model picks it. Asking about 173.172.81.20 in the terms this source covers is enough for it to reach for IPIntelligenceGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`ip`Required	string	The IP address for which you want to get the location data (e.g., 173.172.81.20) ip

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "ip": "173.172.81.20",
    "country": "US",
    "countryName": "United States",
    "region": "MO",
    "regionName": "Missouri",
    "city": "Kansas City",
    "continent": "NA",
    "continentName": "North America",
    "timezone": "America/Chicago",
    "coordinates": [
      39.0831,
      -94.5853
    ],
    "postalCode": "64106",
    "accuracyRadius": 20,
    "isEU": false
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`ip`	string	`173.172.81.20`	The IP address that was looked up
`country`	string	`US`	ISO 3166-1 alpha-2 country code
`countryName`	string	`United States`	Full country name
`region`	string	`MO`	State/region code
`regionName`	string	`Missouri`	Full state/region name
`city`Premium	string	`Kansas City`	City name
`continent`	string	`NA`	Continent code (e.g. NA, EU, AS)
`continentName`	string	`North America`	Full continent name
`timezone`	string	`America/Chicago`	IANA timezone of the IP location
`coordinates`Premium	array	`[39.0831,-94.5853]`	Latitude and longitude
`postalCode`Premium	string	`64106`	Postal/ZIP code of the IP location
`accuracyRadius`Premium	number	`20`	Approximate accuracy radius of the coordinates, in kilometers (lower is more precise)
`isEU`Premium	boolean	`false`	Whether the country is a member of the European Union — useful for GDPR/compliance routing

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at country: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This source is not part of VerveContext. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 5 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Geolocation: Use the IP Lookup API to look up the location of an IP address for geolocation. Use the data to track IP addresses, identify user locations, and analyze traffic patterns
Security Analysis: Look up IP addresses by using the IP Lookup API for security analysis. Use the data to detect suspicious activities, block malicious users, and prevent cyber attacks
Network Monitoring: Monitor networks by using the IP Lookup API to look up IP addresses. Use the data to track network traffic, analyze IP activity, and troubleshoot connectivity issues
Fraud Detection: Detect fraud by using the IP Lookup API to look up IP addresses. Use the data to identify fraudulent activities, block suspicious users, and protect against scams

Other ways to use IP Intelligence Grounding Data

Set up IP Intelligence Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →