Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vitena Directory

REMOTE · API.VITENA.CARE

Search Vitena's public directory of bookable health and wellness professionals

Available components

0 this week 81 Trust /100

Last scanned (21 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 729 tokens (~243/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 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 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
Changelog

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.

  • 19 Oct 26 0
    • Tool “search_providers” rewrote its description, which is the text the model reads security
    • Schema quality: 213 → 243 ▼ functional
    • “search_providers” added an optional parameter “name” cosmetic
  • 28 Sept 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
  • 25 Sept 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
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 22 Sept 26 0
    • “search_providers” reworded the description of “discipline” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 26 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
  • 25 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Aug 26 0

    First indexed and scored.

Diagnostics

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 4 Nov 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 49150 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
MCP tools · 3 exposed · ~665 tokens

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 →

Tool Tokens
get_provider ~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.

NameTypeReqDescription
slugstringyesProfile slug from search_providers, e.g. 'cristobal-diaz'.

No output schema declared.

No examples provided.

list_directory_filters ~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 ~467

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. When the user names a specific professional or practice, pass that as 'name'. Results are public profile data only. Each result includes a profileUrl that can be given to the user for booking.

NameTypeReqDescription
citystring–Deprecated alias for 'location', kept so agents that learned the older argument name keep working. Prefer 'location'.
countrystring–Two-letter ISO country code, e.g. 'TR', 'ES', 'DE'. Narrows an ambiguous place name. Valid values come from 'countries' in list_directory_filters.
disciplinestring–Profession to filter by. One of: dietitian, psychologist, physiotherapist, beauty, child-development, dentist, doctor, other.
languagestring–Two-letter language code the professional consults in, e.g. 'es', 'tr'.
locationstring–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…
namestring–Name of the professional or their practice in free text, e.g. 'Müjde Koyuncu'. Every word must appear in the person's name, the practice name or the profile slug; case and accents are ignored and par…
pageinteger–1-based page number. Page size is fixed at 20.
specializationstring–Specialization CODE (not label) as returned by list_directory_filters.
workModestring–Consultation mode. 'online' for remote, 'in_person' for on-site.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http care-vitena-directory 'https://api.vitena.care/mcp'
Common questions

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 81 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 665 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.