Love Calculator Skill

What this skill does

Add a love-compatibility score to your agent or app. Call it as an MCP tool to return a fun match percentage for any two names. 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 Love Calculator Skill — exactly what your agent gets back when it makes the call.

vervekit · lovecalculatortool call

{
  "name1": "John",
  "name2": "Jane"
}

result

name1: Jane
name2: John
lovePercentage: 62%
response: You have good chemistry. Keep getting to…
additionalText: The love percentage between Jane and Joh…

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

Ways to use it

One toggle, a new capability

Enable Love Calculator and your app or agent can calculate love on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.

A tool agents call themselves

Over MCP, Love Calculator appears to your model as the lovecalculator tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.

REST from any backend

Prefer to call it directly? Any language that can send a GET can hit Love Calculator to calculate love inline in your own server-side code.

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.

lovecalculator

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

Ask your agent

“Enable Love Calculator and ask your agent to calculate love.”
“Give me something fun to show the user.”

Love Calculator Skill, answered

How to connect it over MCP or REST.

How do I add Love Calculator to my app or agent?

Enable the Love Calculator Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the lovecalculator 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 calculate love — 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 Love Calculator appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Love Calculator 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 Love Calculator is available immediately.

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

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

One toggle, a new capability

A tool agents call themselves

REST from any backend

Love Calculator Skill, answered

Give your software a way to act on the world.

Scaling in production?