URL Location Skill
The tool
Let your agent geolocate a URL. Call it as an MCP tool to resolve the hosting country, city and coordinates behind any web address.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as URLLocationSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "URLLocationSkill",
"arguments": {
"url": "https://www.google.com"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about https://www.google.com in the terms this source covers is enough for it to reach for URLLocationSkill on its own.
Connecting
One server URL covers every skill 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": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude Desktop, 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.
| Argument | Type | Example | Description |
|---|---|---|---|
urlRequired | string | https://www.google.com | The URL to lookup the location of. Include the https protocol |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"range": "",
"country": "US",
"region": "",
"city": "Cheney",
"timezone": "America/Chicago",
"state": "Kansas",
"zipcode": "67025",
"coordinates": [
37.751,
-97.822
],
"url": "https://www.merriam-webster.com/dictionary/documentation",
"domain": "www.merriam-webster.com",
"ip": "104.20.45.199",
"countryName": "United States",
"continent": "NA",
"continentName": "North America",
"accuracyRadius": 1000,
"isEU": false
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
rangePremium | string | | IP address range of the server |
country | string | US | Country code where the URL is hosted |
regionPremium | string | | Region or state of the URL's server location |
cityPremium | string | Cheney | City where the URL's server is located |
timezonePremium | string | America/Chicago | Timezone of the URL's server location |
statePremium | string | Kansas | State or province of the server location |
zipcodePremium | string | 67025 | ZIP or postal code of server location |
coordinatesPremium | array | [37.751,-97.822] | Latitude and longitude coordinates of server location |
url | string | https://www.merriam-webster.com/dictionary/documentation | The URL that was looked up |
domain | string | www.merriam-webster.com | The domain extracted from the URL |
ip | string | 104.20.45.199 | The IP address the domain resolves to (first A record) |
countryName | string | United States | Full country name where the URL is hosted |
continent | string | NA | Continent code of the URL's server location |
continentName | string | North America | Full continent name of the URL's server location |
accuracyRadiusPremium | number | 1000 | Approximate accuracy radius (km) of the coordinates |
isEUPremium | boolean | false | Whether the hosting country is in the European Union |
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use URL Location Skill
Set up URL Location Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use URLLocationSkill?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
5 credits each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.