Vitena Directory
REMOTE · API.VITENA.CARE · SCANNED SEP 20
Search Vitena's public directory of bookable health and wellness professionals
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 Security69
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 638 tokens (~212/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Vitena Directory MCP server?
Vitena Directory is a hosted endpoint at https://api.vitena.care/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.vitena.care
claude mcp add --transport http care-vitena-directory 'https://api.vitena.care/mcp'
{
"mcpServers": {
"care-vitena-directory": {
"url": "https://api.vitena.care/mcp"
}
}
} {
"servers": {
"care-vitena-directory": {
"type": "http",
"url": "https://api.vitena.care/mcp"
}
}
} [mcp_servers.care-vitena-directory] url = "https://api.vitena.care/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"care-vitena-directory": {
"type": "remote",
"url": "https://api.vitena.care/mcp",
"enabled": true
}
}
} openclaw mcp add care-vitena-directory --url 'https://api.vitena.care/mcp' --transport streamable-http
mcp_servers:
care-vitena-directory:
url: "https://api.vitena.care/mcp" {
"McpServers": {
"care-vitena-directory": {
"Transport": "http",
"Url": "https://api.vitena.care/mcp"
}
}
} assistant mcp add care-vitena-directory -t streamable-http -u 'https://api.vitena.care/mcp'
{
"mcpServers": {
"care-vitena-directory": {
"type": "http",
"url": "https://api.vitena.care/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 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.
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://api.vitena.care/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vitena.care | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 22 Jun 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 3b62c0e9d72de2c6abacf0375150711 |
| SANs: vitena.care, *.vitena.care | ||||||
| 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.vitena.care. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| care. | present | 17539 | 8 | Verified |
| vitena.care. | absent | 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; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.vitena.care/mcp | Verified | 200 | |
| http (plaintext) | http://api.vitena.care/mcp | Inconclusive | 403 |
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 →
get_provider Get health professional details ~78
Returns the full public profile of one professional by their slug (the value returned as 'slug' by search_providers): services offered, specializations, spoken languages, locations, working hours, contact details and whether online booking is available.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Profile slug from search_providers, e.g. 'cristobal-diaz'. |
No output schema declared.
No examples provided.
list_directory_filters List directory filter options ~120
Returns the valid filter values currently available in the Vitena provider directory: specialization codes (with human labels), spoken-language codes, and the countries that currently have listed professionals. Call this FIRST when you intend to filter a search by specialization — that argument only matches exact codes from this list, so guessing a specialty name will silently return no results. Note that CITY is NOT in this list and does not need to be: search_providers resolves a free-text city, district or region name against a gazetteer, so pass the name the user actually said.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_providers Search health professionals ~376
Searches the public Vitena directory of health and wellness professionals who accept appointments (dietitians, dentists, physiotherapists, psychologists, beauty and aesthetics practitioners, child development specialists). Every filter is optional; with no filters it returns the first page of all publicly listed professionals. Results are public profile data only. Each result includes a profileUrl that can be given to the user for booking.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Deprecated alias for 'location', kept so agents that learned the older argument name keep working. Prefer 'location'. |
| country | string | – | Two-letter ISO country code, e.g. 'TR', 'ES', 'DE'. Narrows an ambiguous place name. Valid values come from 'countries' in list_directory_filters. |
| discipline | string | – | Profession to filter by. One of: dietitian, psychologist, physiotherapist, beauty, child-development, dentist, other. |
| language | string | – | Two-letter language code the professional consults in, e.g. 'es', 'tr'. |
| location | string | – | City, district or region name in free text, e.g. 'Istanbul', 'Kadıköy', 'Madrid', 'Andalucía'. Resolved against a place gazetteer, so it does NOT have to match a fixed list and is NOT returned by lis… |
| page | integer | – | 1-based page number. Page size is fixed at 20. |
| specialization | string | – | Specialization CODE (not label) as returned by list_directory_filters. |
| workMode | string | – | Consultation mode. 'online' for remote, 'in_person' for on-site. |
No output schema declared.
No examples provided.
What is the Vitena Directory MCP server?
Vitena Directory is an MCP server listed in the public MCP registry as care.vitena/directory. Search Vitena's public directory of bookable health and wellness professionals. This page covers its hosted endpoint (https://api.vitena.care/mcp).
Is the Vitena Directory MCP server safe to use?
Vitena Directory scores 80 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 Vitena Directory MCP server expose?
Vitena Directory exposes 3 tools: list_directory_filters, search_providers, get_provider. Their descriptions and schemas cost roughly 574 tokens of context every time the server is loaded.
Does the Vitena Directory MCP server require authentication?
No. We connected to Vitena Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vitena Directory MCP server still maintained?
Vitena Directory 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.