Vitena Directory MCP

This official MCP server provides a read-only interface to Vitena's public directory of health and wellness professionals. It allows AI agents to search for providers by discipline, location, and other filters, and retrieve specific provider details without accessing any private client or health data.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Vitena

MCP endpoint (Streamable HTTP)

https://api.vitena.care/mcp

Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 3 of 3 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 1:42 PM UTC
Passed Official MCP Registry namespace is tied to vitena.care · Nov 6, 2026, 1:23 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 1:23 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Search for health professionals by discipline and city
Retrieve public profiles of listed practitioners
Filter providers by language or consultation mode

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: care.vitena/directory@1.0.0 Project website

Protocol and capabilities

Server: vitena-directory 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 3 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Vitena's public directory of bookable health and wellness professionals across Europe and Turkey. Use list_directory_filters to learn valid city and specialization values, search_providers to find professionals, and get_provider for one professional's full public profile. All data is public; nothing here is patient or medical-record data.

Tools

3 advertised

list_directory_filters — List directory filter options

Advertised by the server during the last successful anonymous check.

Advertised read-onlyOpen-world

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.

list_directory_filters input schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

list_directory_filters annotations

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

search_providers — Search health professionals

Advertised by the server during the last successful anonymous check.

Advertised read-onlyOpen-world

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.

search_providers input schema

{
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "Deprecated alias for 'location', kept so agents that learned the older argument name keep working. Prefer 'location'."
    },
    "name": {
      "type": "string",
      "description": "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 part of a word is enough ('koyun'). Names that start with the given words come first."
    },
    "page": {
      "type": "integer",
      "minimum": 1,
      "description": "1-based page number. Page size is fixed at 20."
    },
    "country": {
      "type": "string",
      "description": "Two-letter ISO country code, e.g. 'TR', 'ES', 'DE'. Narrows an ambiguous place name. Valid values come from 'countries' in list_directory_filters."
    },
    "language": {
      "type": "string",
      "description": "Two-letter language code the professional consults in, e.g. 'es', 'tr'."
    },
    "location": {
      "type": "string",
      "description": "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 list_directory_filters — pass the place the user actually named. Choosing a region matches everywhere inside it. An unrecognised place returns an explanatory error rather than silently ignoring the filter."
    },
    "workMode": {
      "enum": [
        "online",
        "in_person"
      ],
      "type": "string",
      "description": "Consultation mode. 'online' for remote, 'in_person' for on-site."
    },
    "discipline": {
      "enum": [
        "dietitian",
        "psychologist",
        "physiotherapist",
        "beauty",
        "child-development",
        "dentist",
        "doctor",
        "other"
      ],
      "type": "string",
      "description": "Profession to filter by. One of: dietitian, psychologist, physiotherapist, beauty, child-development, dentist, doctor, other."
    },
    "specialization": {
      "type": "string",
      "description": "Specialization CODE (not label) as returned by list_directory_filters."
    }
  },
  "additionalProperties": false
}

search_providers annotations

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

get_provider — Get health professional details

Advertised by the server during the last successful anonymous check.

Advertised read-onlyOpen-world

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.

get_provider input schema

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Profile slug from search_providers, e.g. 'cristobal-diaz'."
    }
  },
  "additionalProperties": false
}

get_provider annotations

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-06: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 996 ms
95th percentile latency: 996 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 1:42 PM UTC · probe · passed · 996 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http vitena-directory-mcp https://api.vitena.care/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add vitena-directory-mcp --url https://api.vitena.care/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable vitena-directory-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "vitena-directory-mcp": {
      "url": "https://api.vitena.care/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "vitena-directory-mcp": {
      "type": "streamableHttp",
      "url": "https://api.vitena.care/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start vitena-directory-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "vitena-directory-mcp": {
      "type": "http",
      "url": "https://api.vitena.care/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http vitena-directory-mcp https://api.vitena.care/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://api.vitena.care/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "vitena-directory-mcp": {
      "serverUrl": "https://api.vitena.care/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Vitena Directory MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 1,148

Do you run Vitena Directory MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing

Vitena Directory MCP

Endpoint and access

What its tools do

Read-only (3)

Checks and signals

What you can do with it

Source and maintenance

Protocol and capabilities

Server-provided instructions

Tools

Prompts

Resources

90-day uptime

30-day availability

Maintenance history

Connect from your client

Claude Code

Codex

Cursor

Cline

VS Code

Gemini CLI

Claude Desktop

Windsurf

Let your agent find its tools

Other crm, sales, and marketing servers

Do you run Vitena Directory MCP?