URL Location SkillURL Location Skill

OnlineCredit Usage:5 per callTool:URLLocationSkill

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.

Tool call
{
  "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.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-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.

ArgumentTypeExampleDescription
urlRequiredstringhttps://www.google.comThe 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.

Result
{
  "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

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
rangePremiumstringIP address range of the server
countrystringUSCountry code where the URL is hosted
regionPremiumstringRegion or state of the URL's server location
cityPremiumstringCheneyCity where the URL's server is located
timezonePremiumstringAmerica/ChicagoTimezone of the URL's server location
statePremiumstringKansasState or province of the server location
zipcodePremiumstring67025ZIP or postal code of server location
coordinatesPremiumarray[37.751,-97.822]Latitude and longitude coordinates of server location
urlstringhttps://www.merriam-webster.com/dictionary/documentationThe URL that was looked up
domainstringwww.merriam-webster.comThe domain extracted from the URL
ipstring104.20.45.199The IP address the domain resolves to (first A record)
countryNamestringUnited StatesFull country name where the URL is hosted
continentstringNAContinent code of the URL's server location
continentNamestringNorth AmericaFull continent name of the URL's server location
accuracyRadiusPremiumnumber1000Approximate accuracy radius (km) of the coordinates
isEUPremiumbooleanfalseWhether 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.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief 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.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?