Moonrise & Moonset Skill

What this skill does

Give your agent lunar timing. Call it as an MCP tool to read moonrise, moonset and moon phase for any location and date. 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 Moonrise & Moonset Skill — exactly what your agent gets back when it makes the call.

vervekit · moonrisemoonsettool call

{
  "lat": 37.7749,
  "lon": -122.4194,
  "date": "01-16-2026"
}

result

coordinates: { … }
phase: Waning Crescent
moonrise: 2025-12-16T12:24:41.532Z
moonset: 2025-12-16T22:22:04.027Z
moonAlwaysUp: false
moonAlwaysDown: false

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

Ways to use it

Add weather without a provider

Give your app the ability to add moonrise & moonset to your app by enabling one skill instead of signing up for a weather API and wiring its SDK. Same key as every other skill.

An agent tool for conditions

Over MCP, your model calls the moonrisemoonset tool when a task needs live conditions — trip planning, logistics, scheduling — without any per-source plumbing.

REST from any backend

Node, Python, Go — anything that can send a GET can call Moonrise & Moonset directly, so a server-side job can add moonrise & moonset to your app in one request.

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.

moonrisemoonset

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/moonrisemoonset

Ask your agent

“Enable Moonrise & Moonset and ask your agent to add moonrise & moonset to your app.”
“What's the weather in Tokyo right now?”

Moonrise & Moonset Skill, answered

How to connect it over MCP or REST.

How do I add Moonrise & Moonset to my app or agent?

Enable the Moonrise & Moonset Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the moonrisemoonset 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 moonrise & moonset 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 Moonrise & Moonset appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Moonrise & Moonset 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 Moonrise & Moonset is available immediately.

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

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

Add weather without a provider

An agent tool for conditions

REST from any backend

Moonrise & Moonset Skill, answered

Give your software a way to act on the world.

Scaling in production?