
Bodymeasure
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Anthropometric predictions and percentile lookups via the Humanform API.
Overview
Bodymeasure's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Bodymeasure in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
bodymeasure
How tall is a 30-year-old man at the 50th percentile in the US? And which percentile does a measured popliteal height of 43.1 cm land on for a 34-year-old woman? bodymeasure asks the Humanform API — a service of anthropometric reference data — and returns its answers as JSON, in both directions:
- Forward: give a percentile, get the measurement value that sits there for a person of a given sex, age, and country.
- Reverse: give a measured value, get the percentile it falls on for that same kind of person.
Two catalogue calls round out the surface: the measurement names and body groups the API supports, and its country codes and labels.
Configuration
You bring your own Humanform API key:
Without it, bodymeasure does not guess: every call fails with
HUMANFORM_API_KEY is not set, no request is made, and no
measurement is invented. HUMANFORM_API_URL overrides the
API base URL (https://api.humanform.app by default).
CLI
Each subcommand takes its arguments as one JSON string; the
two list commands take "{}".
Output is the Humanform payload as JSON. Exit codes: 0 on
success, 1 on a runtime error (including a missing key, a
validation failure, or an upstream error), 2 on a usage
error.
Arguments are checked before any request: string arguments
must be non-empty, age must be a finite number greater
than 0, percentile must lie strictly between 0 and 100, and
a lookup value must be finite. When the API itself answers
with an error body carrying error and message fields,
that pair is reported as <error>: <message>.
MCP server
MCP client config:
Tools
predict_measurement— Forward lookup: percentile → measurement value. Requiresmeasurement,sex,age,percentile,country, andunit.percentile_lookup— Reverse lookup: measured value → percentile. Requiresmeasurement,sex,age,country,unit, andvalue.list_measurements— List all supported measurement names and body groups. No arguments.list_countries— List supported country codes and labels. No arguments.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit 3f46f3d
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts