Dr. Dotzauer Calculators
REMOTE · DRDOTZAUER.DE
Free calculators for body composition, calories, protein and strength, with source links.
Available components
Last scanned (23 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1357 tokens (~123/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +2
- DNSSEC: fail → pass ▲ security
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://drdotzauer.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=drdotzauer.de | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6a526e8b3cd48259130f43b3e7f82df6 |
| SANs: drdotzauer.de | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of drdotzauer.de. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| de. | DS published | 26755 | 8 | Verified |
| drdotzauer.de. | DS published | 2371 | 13 | Verified |
| drdotzauer.de. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://drdotzauer.de/mcp | Verified | 200 | |
| http (plaintext) | http://drdotzauer.de/mcp | HTTPS enforced | 308 | https://drdotzauer.de/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
abnehmdauer ~127
Dauer bis zum Zielgewicht bei drei Tempos (0,5 / 1 / 1,5 % Körpergewicht pro Woche), optional mit Termin-Prüfung. Wie der Abnehmdauer-Rechner auf drdotzauer.de/abnehmen/abnehmdauer.
| Name | Type | Req | Description |
|---|---|---|---|
| current_weight_kg | number | yes | Aktuelles Gewicht in kg |
| deadline_weeks | number | – | Optional: Wochen bis zu einem Termin, prüft das nötige Wochentempo |
| goal_weight_kg | number | yes | Wunschgewicht in kg (kleiner als aktuell) |
No output schema declared.
No examples provided.
bmi ~64
Body-Mass-Index (kg/m²) mit WHO-Klassifikation für Erwachsene. Wie der BMI-Rechner auf drdotzauer.de/bmi-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| height_cm | number | yes | Größe in cm |
| weight_kg | number | yes | Gewicht in kg |
No output schema declared.
No examples provided.
einrm ~103
Geschätztes 1-Rep-Maximum (1RM) und 5RM-Äquivalent aus Gewicht × sauberen Wiederholungen (Mittel aus Epley- und Brzycki-Formel). Wie der 1RM-Rechner auf drdotzauer.de/kraftwerte-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| reps | number | yes | Saubere Wiederholungen (2–12) |
| weight_kg | number | yes | Bewegtes Gewicht in kg |
No output schema declared.
No examples provided.
ffmi ~116
Fat-Free-Mass-Index (FFMI) und Magermasse aus Gewicht, Größe und Körperfettanteil, normalisiert auf 1,80 m (Kouri 1995, Faktor 6,3). Wie der FFMI-Rechner auf drdotzauer.de/ffmirechner.
| Name | Type | Req | Description |
|---|---|---|---|
| body_fat_percent | number | yes | Körperfettanteil in % (2–60) |
| height_cm | number | yes | Größe in cm |
| weight_kg | number | yes | Gewicht in kg |
No output schema declared.
No examples provided.
grundumsatz ~133
Grundumsatz (BMR, Mifflin-St-Jeor + Harris-Benedict-Vergleich) und Gesamtumsatz (TDEE) je Aktivitätslevel. Wie der Grundumsatz-Rechner auf drdotzauer.de/grundumsatz-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Aktivitätslevel (sedentary 1.2 … athlete 1.9); Default light |
| age_years | number | yes | Alter in Jahren (14–100) |
| height_cm | number | yes | – |
| sex | string | yes | – |
| weight_kg | number | yes | – |
No output schema declared.
No examples provided.
idealgewicht ~64
Gesunde Gewichtsspanne (kg) für eine Körpergröße über die BMI-Spanne 18,5 bis 24,9. Wie der Idealgewicht-Rechner auf drdotzauer.de/idealgewicht-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| height_cm | number | yes | Größe in cm |
No output schema declared.
No examples provided.
kaloriendefizit ~148
Gesamtumsatz (TDEE) plus drei Defizit-Stufen (−15/−20/−25 %) mit erwarteter Wochen-Abnahme und Eiweißziel. Enthält ein Erwachsenen-/Plausibilitäts-Gate (kein Zahlenziel bei Minderjährigen oder Untergewicht). Wie der Kaloriendefizit-Rechner auf drdotzauer.de/kaloriendefizit-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Aktivitätslevel; Default light |
| age_years | number | yes | Alter in Jahren (14–100) |
| height_cm | number | yes | – |
| sex | string | yes | – |
| weight_kg | number | yes | – |
No output schema declared.
No examples provided.
kalorienverbrauch ~134
Kalorienverbrauch EINER Sport-/Alltagsaktivität (MET-basiert: kcal = MET × kg × Stunden). Nicht der Gesamtumsatz, dafür grundumsatz/kaloriendefizit nutzen. Wie der Kalorienverbrauch-Rechner auf drdotzauer.de/kalorienverbrauch-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Aktivität (setzt den MET-Wert); alternativ met direkt angeben |
| duration_min | number | yes | Dauer in Minuten (1–600) |
| met | number | – | Optionaler MET-Wert, überschreibt activity |
| weight_kg | number | yes | – |
No output schema declared.
No examples provided.
koerperfett_navy ~163
Körperfettanteil (%) nach der US-Navy-Umfangmethode aus Körpermaßen berechnen (Größe, Hals, Taille/Bauch, bei Frauen zusätzlich Hüfte), inkl. neutraler Kategorie-Einordnung. Gleiche Formel wie der Körperfett-Rechner auf drdotzauer.de/koerperfett-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| height_cm | number | yes | Körpergröße in cm |
| hip_cm | number | – | Hüftumfang in cm (nur bei sex=female Pflicht) |
| neck_cm | number | yes | Halsumfang in cm |
| sex | string | yes | Biologisches Geschlecht |
| waist_cm | number | yes | Taillen- (Frauen) bzw. Bauchumfang (Männer) in cm |
No output schema declared.
No examples provided.
kraftwerte ~208
Kraftstandards relativ zum Körpergewicht (Anfänger/Fortgeschritten/Elite) für Kniebeuge, Bankdrücken, Kreuzheben, Rudern, Schulterdrücken (5RM in kg) und Klimmzüge (Wdh.), plus Gesamtbewertung. Wie der Kraftwerte-Rechner auf drdotzauer.de/kraftwerte-rechner.
| Name | Type | Req | Description |
|---|---|---|---|
| bench | number | – | 5RM Bankdrücken in kg (optional) |
| bodyweight_kg | number | yes | Körpergewicht in kg (30–200) |
| deadlift | number | – | 5RM Kreuzheben in kg (optional) |
| ohp | number | – | 5RM Schulterdrücken in kg (optional) |
| pullups | number | – | Maximale Klimmzüge (Wdh., optional) |
| row | number | – | 5RM Rudern in kg (optional) |
| sex | string | yes | – |
| squat | number | – | 5RM Kniebeuge in kg (optional) |
No output schema declared.
No examples provided.
protein_bedarf ~97
Täglicher Eiweißbedarf als Bereich (g/Tag) nach Gewicht, Ziel und Aktivität (Faktoren u. a. Morton 2018). Wie der Proteinrechner auf drdotzauer.de/proteinrechner.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Sportlich aktiv? Nur bei goal=erhalt relevant, Default true |
| goal | string | yes | Ziel |
| weight_kg | number | yes | – |
No output schema declared.
No examples provided.
How do I install the Dr. Dotzauer Calculators MCP server?
Dr. Dotzauer Calculators is a hosted endpoint at https://drdotzauer.de/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · drdotzauer.de
claude mcp add --transport http de-drdotzauer-health-calculators 'https://drdotzauer.de/mcp'
What is the Dr. Dotzauer Calculators MCP server?
Dr. Dotzauer Calculators is an MCP server listed in the public MCP registry as de.drdotzauer/health-calculators. Free calculators for body composition, calories, protein and strength, with source links. This page covers its hosted endpoint (https://drdotzauer.de/mcp).
Is the Dr. Dotzauer Calculators MCP server safe to use?
Dr. Dotzauer Calculators scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Dr. Dotzauer Calculators MCP server expose?
Dr. Dotzauer Calculators exposes 11 tools: koerperfett_navy, bmi, ffmi, idealgewicht, grundumsatz, and 6 more. Their descriptions and schemas cost roughly 1,357 tokens of context every time the server is loaded.
Does the Dr. Dotzauer Calculators MCP server require authentication?
No. We connected to Dr. Dotzauer Calculators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dr. Dotzauer Calculators MCP server still maintained?
Dr. Dotzauer Calculators is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Dr. Dotzauer Calculators MCP server?
VerifyMCP ran 12 checks on Dr. Dotzauer Calculators, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Dr. Dotzauer Calculators: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.