AMITA – Termin zur ärztlichen Abnehmberatung
REMOTE · API.RESETHEALTHAPP.COM
Find AMITA weight-loss doctors in Germany and book the free first consultation.
Available components
Last scanned (17 hours ago)
Scores higher than 61% 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 548 tokens (~182/item across 3 items; 3 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “book_consultation” rewrote its description, which is the text the model reads security
- Tool “find_practices” rewrote its description, which is the text the model reads security
- Tool “list_free_slots” rewrote its description, which is the text the model reads security
- Schema quality: 159 → 182 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “book_consultation” reworded the description of “practiceId” cosmetic
- “book_consultation” reworded the description of “privacyPolicyAccepted” cosmetic
- “book_consultation” reworded the description of “slotIso” cosmetic
- “find_practices” reworded the description of “location” cosmetic
- “list_free_slots” reworded the description of “practiceId” cosmetic
- “find_practices” made “location” optional cosmetic
- Tool “book_consultation” changed its title: Book first consultation cosmetic
- Tool “find_practices” changed its title: Find AMITA practices cosmetic
- Tool “list_free_slots” changed its title: Show free consultation times cosmetic
- 16 Nov 26 72
First indexed and scored.
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://api.resethealthapp.com/v2/agent-booking/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.resethealthapp.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 14 Sept 2026 | 30 Mar 2027 | RSA 2048 | SHA256-RSA | 8955f4836cc106f250a46094f8058a9 |
| SANs: *.resethealthapp.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.resethealthapp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| resethealthapp.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.resethealthapp.com/v2/agent-booking/mcp | Verified | 200 | |
| http (plaintext) | http://api.resethealthapp.com/v2/agent-booking/mcp | HTTPS enforced | 301 | https://api.resethealthapp.com:443/v2/agent-booking/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 →
book_consultation Book first consultation ~176
Use this when the person has chosen a practice and time and wants to book. Books the non-binding first consultation with a doctor with the person's own name, e-mail and phone number and their agreement to AMITA's privacy policy; AMITA e-mails the confirmation. Cannot change or cancel an appointment.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| firstName | string | yes | – |
| lastName | string | yes | – |
| phone | string | yes | Phone number for the practice team, ideally mobile. |
| practiceId | string | yes | Id of an AMITA practice. |
| privacyPolicyAccepted | boolean | yes | Whether the person agreed to AMITA's privacy policy (https://abnehmen-mit-arzt.de/privacy/). |
| slotIso | string | yes | Start of a free consultation slot of this practice (ISO 8601). |
No output schema declared.
No examples provided.
find_practices Find AMITA practices ~109
Use this when someone wants a doctor for medical weight loss or an AMITA practice in Germany. Returns the nearest AMITA practices with address, doctor, distance and next free time; locationFound is false when no place was recognised. Not for medical advice, prescriptions or emergencies.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Search area the person named: city, district or German postcode, e.g. "Berlin Moabit" or "10551". Without it the search uses the approximate location the client shares. |
No output schema declared.
No examples provided.
list_free_slots Show free consultation times ~53
Use this when the person wants appointment times at one AMITA practice. Returns its free consultation times for the next two weeks (Europe/Berlin).
| Name | Type | Req | Description |
|---|---|---|---|
| practiceId | string | yes | Id of an AMITA practice. |
No output schema declared.
No examples provided.
How do I install the AMITA – Termin zur ärztlichen Abnehmberatung MCP server?
AMITA – Termin zur ärztlichen Abnehmberatung is a hosted endpoint at https://api.resethealthapp.com/v2/agent-booking/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 · api.resethealthapp.com
claude mcp add --transport http de-abnehmen-mit-arzt-termine 'https://api.resethealthapp.com/v2/agent-booking/mcp'
What is the AMITA – Termin zur ärztlichen Abnehmberatung MCP server?
AMITA – Termin zur ärztlichen Abnehmberatung is an MCP server listed in the public MCP registry as de.abnehmen-mit-arzt/termine. Find AMITA weight-loss doctors in Germany and book the free first consultation. This page covers its hosted endpoint (https://api.resethealthapp.com/v2/agent-booking/mcp).
Is the AMITA – Termin zur ärztlichen Abnehmberatung MCP server safe to use?
AMITA – Termin zur ärztlichen Abnehmberatung scores 74 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 AMITA – Termin zur ärztlichen Abnehmberatung MCP server expose?
AMITA – Termin zur ärztlichen Abnehmberatung exposes 3 tools: find_practices, list_free_slots, book_consultation. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.
Does the AMITA – Termin zur ärztlichen Abnehmberatung MCP server require authentication?
No. We connected to AMITA – Termin zur ärztlichen Abnehmberatung without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AMITA – Termin zur ärztlichen Abnehmberatung MCP server still maintained?
AMITA – Termin zur ärztlichen Abnehmberatung 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 AMITA – Termin zur ärztlichen Abnehmberatung MCP server?
VerifyMCP ran 13 checks on AMITA – Termin zur ärztlichen Abnehmberatung, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.