World Time Skill

What this skill does

Give your agent the current time anywhere. Call it as an MCP tool to read the live local time, date and timezone for any city on Earth. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the World Time Skill — exactly what your agent gets back when it makes the call.

vervekit · worldtimetool call

{
  "city": "San Francisco"
}

result

search: San Francisco
foundCities: [ 2 items ]

Run it with your own input. Live calls happen in your dashboard, on your key.

Sign in to try

Ways to use it

Turn IDs into detail

Enable World Time and your app can add world time to your app — expand an identifier into full structured detail — in a single call, no integration per source.

A tool your agent reaches for

Over MCP, your model calls worldtime to enrich data mid-workflow exactly when it's needed.

Enrich from your backend

Call World Time over REST to add world time to your app across a batch in a server-side job, one key for all of it.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

worldtime

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/worldtime

Ask your agent

“Enable World Time and ask your agent to add world time to your app.”
“Use the World Time skill for me.”

World Time Skill, answered

How to connect it over MCP or REST.

How do I add World Time to my app or agent?

Enable the World Time Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the worldtime tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add world time to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so World Time appears as a standard tool with nothing skill-specific to integrate.

How many credits does a World Time call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and World Time is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; World Time is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

More Data Lookup skills

Browse all skills

Turn IDs into detail

A tool your agent reaches for

Enrich from your backend

World Time Skill, answered

Give your software a way to act on the world.

Scaling in production?