Anteos Health — Medical Appointment Booking
REMOTE · ANTEOSHEALTH.COM · SCANNED SEP 20
Book medical appointments with French doctors by specialty and city via AI agents.
Available components
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1675 tokens (~167/item across 10 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the Anteos Health — Medical Appointment Booking MCP server?
Anteos Health — Medical Appointment Booking is a hosted endpoint at https://anteoshealth.com/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 · anteoshealth.com
claude mcp add --transport http anteos-health-anteos-booking 'https://anteoshealth.com/mcp'
{
"mcpServers": {
"anteos-health-anteos-booking": {
"url": "https://anteoshealth.com/mcp"
}
}
} {
"servers": {
"anteos-health-anteos-booking": {
"type": "http",
"url": "https://anteoshealth.com/mcp"
}
}
} [mcp_servers.anteos-health-anteos-booking] url = "https://anteoshealth.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"anteos-health-anteos-booking": {
"type": "remote",
"url": "https://anteoshealth.com/mcp",
"enabled": true
}
}
} openclaw mcp add anteos-health-anteos-booking --url 'https://anteoshealth.com/mcp' --transport streamable-http
mcp_servers:
anteos-health-anteos-booking:
url: "https://anteoshealth.com/mcp" {
"McpServers": {
"anteos-health-anteos-booking": {
"Transport": "http",
"Url": "https://anteoshealth.com/mcp"
}
}
} assistant mcp add anteos-health-anteos-booking -t streamable-http -u 'https://anteoshealth.com/mcp'
{
"mcpServers": {
"anteos-health-anteos-booking": {
"type": "http",
"url": "https://anteoshealth.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://anteoshealth.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anteoshealth.com | CN=YE1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5070c8566e0b6b774563c19afc6d1b1ad06 |
| SANs: anteoshealth.com, www.anteoshealth.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of anteoshealth.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| anteoshealth.com. | present | 46945 | 8 | Verified |
| anteoshealth.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Anteos MCP", charset="UTF-8", resource_metadata="https://anteoshealth.com/.well-known/oauth-protected-resource"
Bearer realm="Anteos MCP", charset="UTF-8", resource_metadata="https://anteoshealth.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self' https: data: blob:;script-src 'self' https:;style-src 'self' https: 'unsafe-inline';img-src 'self' data: blob: https:;font-src 'self' data: https:;connect-src 'self' https: wss:;base-uri 'self';form-action 'self';frame-ancestors 'self';object-src 'none';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self) |
Protected resource metadata
| Document | https://anteoshealth.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | No |
| Problem | metadata_malformed |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://anteoshealth.com/mcp | Verified | 200 | |
| http (plaintext) | http://anteoshealth.com/mcp | HTTPS enforced | 301 | https://anteoshealth.com/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_appointment ~371
Prend un rendez-vous pour un patient chez un médecin Anteos. Le rendez-vous est immédiatement confirmé dans l'agenda du médecin.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date du rendez-vous au format YYYY-MM-DD (ex: "2026-04-20") |
| doctor_id | string | yes | Identifiant du médecin (obtenu via search_doctors) |
| motif | string | – | Motif de la consultation en texte libre (optionnel, ex: "Suivi traitement", "Renouvellement ordonnance") |
| motif_id | string | – | Identifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Détermine la durée du RDV et est enregistré dans l'agenda du médecin. |
| patient_dob | string | yes | Date de naissance du patient au format YYYY-MM-DD. Obligatoire. |
| patient_email | string | yes | Email du patient — OBLIGATOIRE. Utilisé pour l'envoi de la confirmation et des rappels de rendez-vous. |
| patient_firstname | string | yes | Prénom du patient |
| patient_lastname | string | yes | Nom de famille du patient (en majuscules de préférence) |
| patient_phone | string | – | Téléphone du patient (optionnel — format: 0612345678 ou +33612345678) |
| patient_sex | string | yes | Sexe du patient : M (Masculin), F (Féminin) ou autre. Obligatoire. |
| send_confirmation_email | boolean | – | Envoyer un email de confirmation au patient avec des liens de gestion du RDV. Défaut: true. Passer false si votre plateforme envoie sa propre confirmation. |
| time | string | yes | Heure du rendez-vous au format HH:MM (ex: "14:30") |
No output schema declared.
No examples provided.
cancel_appointment ~84
Annule un rendez-vous existant. L'annulation est définitive. Requiert le appointment_token reçu lors de la réservation (book_appointment).
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | Identifiant unique du rendez-vous à annuler |
| appointment_token | string | yes | Token de sécurité reçu dans la réponse de book_appointment. Révoqué définitivement après annulation. |
No output schema declared.
No examples provided.
find_next_available ~288
Cherche les prochains créneaux disponibles sur une période, pour un ou plusieurs médecins filtrés par spécialité et/ou ville. À préférer à get_available_slots quand l'utilisateur demande "quand est-ce que X est libre" ou "y a-t-il un RDV disponible cette semaine". Retourne au maximum max_slots créneaux par médecin pour ne pas surcharger le contexte.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Ville (ex: "Paris"). Ignoré si doctor_id est fourni. |
| days | integer | – | Nombre de jours à couvrir depuis from_date (défaut: 7, max: 30) |
| doctor_id | string | – | Chercher uniquement pour ce médecin (obtenu via search_doctors). Court-circuite specialty et city. |
| from_date | string | yes | Date de début de la recherche au format YYYY-MM-DD |
| max_slots | integer | – | Nombre maximum de créneaux retournés par médecin (défaut: 5, max: 20) |
| motif_id | string | – | Identifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Adapte la grille de créneaux à la durée du motif. |
| specialty | string | – | Spécialité médicale (ex: "neurologue", "cardiologue"). Ignoré si doctor_id est fourni. |
No output schema declared.
No examples provided.
get_appointment ~113
Récupère les informations et le statut d'un rendez-vous. Requiert le appointment_token reçu lors de la réservation (book_appointment) — ce token prouve que l'appelant représente le patient concerné.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | Identifiant unique du rendez-vous (obtenu via book_appointment) |
| appointment_token | string | yes | Token de sécurité reçu dans la réponse de book_appointment. À stocker côté client et à transmettre ici pour prouver l'identité du patient. |
No output schema declared.
No examples provided.
get_available_slots ~130
Retourne les créneaux disponibles pour un médecin à une date donnée. À appeler avant book_appointment pour proposer des options concrètes au patient plutôt que de réserver à l'aveugle.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date au format YYYY-MM-DD (ex: "2026-05-10") |
| doctor_id | string | yes | Identifiant du médecin (obtenu via search_doctors) |
| motif_id | string | – | Identifiant du motif de consultation (optionnel, obtenu via get_doctor_profile). Adapte la grille de créneaux à la durée du motif. |
No output schema declared.
No examples provided.
get_doctor_profile ~107
Retourne le profil complet d'un médecin : coordonnées, secteur conventionnement, carte vitale, tiers payant, téléconsultation, langues, description, diplômes, expertises, avis patients Anteos (note, résumé IA), et créneaux disponibles sur les 7 prochains jours. À appeler après search_doctors pour aider le patient à choisir son médecin.
| Name | Type | Req | Description |
|---|---|---|---|
| doctor_id | string | yes | Identifiant du médecin (champ "id" retourné par search_doctors) |
No output schema declared.
No examples provided.
list_my_appointments ~128
Liste les rendez-vous créés par cette clé partenaire. Utile pour récupérer l'état après un crash ou un redémarrage de l'agent, ou pour vérifier les RDV en cours sans stocker les tokens côté client.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Nombre de résultats par page (défaut: 20, max: 100) |
| offset | integer | – | Décalage pour la pagination (défaut: 0) |
| status | string | – | Filtrer par statut temporel : "upcoming" (par défaut), "past" ou "all" |
No output schema declared.
No examples provided.
reschedule_appointment ~142
Reporte un rendez-vous existant vers un nouveau créneau. L'opération est atomique : l'ancien RDV est annulé et le nouveau est créé en une seule transaction, évitant qu'un autre agent prenne le créneau cible entre les deux. Un nouveau appointment_token est émis — l'ancien est révoqué définitivement.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | Identifiant du rendez-vous à reporter |
| appointment_token | string | yes | Token de sécurité reçu lors de la réservation initiale |
| new_date | string | yes | Nouvelle date au format YYYY-MM-DD |
| new_time | string | yes | Nouvelle heure au format HH:MM |
No output schema declared.
No examples provided.
resend_appointment_token ~92
Renvoie par email au patient le lien de gestion de son rendez-vous. À utiliser si le appointment_token n'est plus disponible côté client. Le token n'est jamais renvoyé dans la réponse — uniquement par email au patient.
| Name | Type | Req | Description |
|---|---|---|---|
| appointment_id | string | yes | Identifiant unique du rendez-vous |
| patient_email | string | yes | Email du patient enregistré lors de la réservation. Doit correspondre exactement. |
No output schema declared.
No examples provided.
search_doctors ~220
Recherche des médecins Anteos par spécialité et/ou ville. Retourne les médecins avec disponibilités, secteur conventionnement et informations pratiques. Utilisez get_doctor_profile avec le champ id pour obtenir le profil complet d'un médecin (avis patients, diplômes, langues, tarifs).
| Name | Type | Req | Description |
|---|---|---|---|
| available_from | string | – | Si fourni, ne retourne que les médecins ayant au moins un créneau libre à partir de cette date (YYYY-MM-DD). Utile pour filtrer d'emblée sur la disponibilité. |
| city | string | – | Ville où rechercher (ex: "Paris", "Lyon") |
| limit | integer | – | Nombre maximum de résultats par page (défaut: 10, max: 50) |
| offset | integer | – | Décalage pour la pagination (défaut: 0). Utiliser limit+offset pour naviguer au-delà de la première page. |
| specialty | string | – | Spécialité médicale (ex: "médecin généraliste", "dermatologue", "cardiologue") |
No output schema declared.
No examples provided.
What is the Anteos Health — Medical Appointment Booking MCP server?
Anteos Health — Medical Appointment Booking is an MCP server listed in the public MCP registry as io.github.Anteos-Health/anteos-booking. Book medical appointments with French doctors by specialty and city via AI agents. This page covers its hosted endpoint (https://anteoshealth.com/mcp).
Is the Anteos Health — Medical Appointment Booking MCP server safe to use?
Anteos Health — Medical Appointment Booking scores 92 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 Anteos Health — Medical Appointment Booking MCP server expose?
Anteos Health — Medical Appointment Booking exposes 10 tools: search_doctors, book_appointment, find_next_available, get_available_slots, get_appointment, and 5 more. Their descriptions and schemas cost roughly 1,675 tokens of context every time the server is loaded.
Does the Anteos Health — Medical Appointment Booking MCP server require authentication?
Yes. Anteos Health — Medical Appointment Booking asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Anteos Health — Medical Appointment Booking MCP server still maintained?
Anteos Health — Medical Appointment Booking is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.