BMI & Fitness Metrics Skill

What this skill does

Give your agent body metrics. Call it as an MCP tool to compute BMI, BMR, TDEE, calorie targets and macros from height, weight and age. 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 BMI & Fitness Metrics Skill — exactly what your agent gets back when it makes the call.

vervekit · bmicalculatortool call

{
  "weight": 180,
  "height": 70,
  "unit": "imperial",
  "age": 30,
  "gender": "male",
  "activityLevel": "moderate"
}

result

height: 170 cm
weight: 70 kg
bmi: 24.221453287197235
risk: Low risk
summary: This weight is normal and you are healthy.
recommendation: A BMI between 18.5 and 24.9 falls within…

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 BMI & Fitness Metrics and your app or agent can add bmi & fitness metrics to your app 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, BMI & Fitness Metrics appears to your model as the bmicalculator 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 BMI & Fitness Metrics to add bmi & fitness metrics to your app 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.

bmicalculator

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

Ask your agent

“Enable BMI & Fitness Metrics and ask your agent to add bmi & fitness metrics to your app.”
“Use the BMI & Fitness Metrics skill for me.”

BMI & Fitness Metrics Skill, answered

How to connect it over MCP or REST.

How do I add BMI & Fitness Metrics to my app or agent?

Enable the BMI & Fitness Metrics Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the bmicalculator 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 bmi & fitness metrics 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 BMI & Fitness Metrics appears as a standard tool with nothing skill-specific to integrate.

How many credits does a BMI & Fitness Metrics 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 BMI & Fitness Metrics is available immediately.

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

VerveKit runs on APIVerve, our production data engine; BMI & Fitness Metrics 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

BMI & Fitness Metrics Skill, answered

Give your software a way to act on the world.

Scaling in production?