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.

com.takident/patient-services

REMOTE · MCP.TAKIDENT.COM · SCANNED SEP 22

MCP server exposing structured data and tools for Taki Dent Patient Services (takident.com).

Available components

0 this week 80 Trust /100
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 Security60
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 905 tokens (~75/item across 12 items; 12 tools + 0 resources), lean.Pass
  • 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 Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.takident/patient-services MCP server?

com.takident/patient-services is a hosted endpoint at https://mcp.takident.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 · mcp.takident.com

# add to Claude Code
claude mcp add --transport http com-takident-patient-services 'https://mcp.takident.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-takident-patient-services": {
      "url": "https://mcp.takident.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-takident-patient-services": {
      "type": "http",
      "url": "https://mcp.takident.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-takident-patient-services]
url = "https://mcp.takident.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-takident-patient-services": {
      "type": "remote",
      "url": "https://mcp.takident.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-takident-patient-services --url 'https://mcp.takident.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-takident-patient-services:
    url: "https://mcp.takident.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-takident-patient-services": {
      "Transport": "http",
      "Url": "https://mcp.takident.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-takident-patient-services -t streamable-http -u 'https://mcp.takident.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-takident-patient-services": {
      "type": "http",
      "url": "https://mcp.takident.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 12 Sept 26 0
    • Stability: 0.97 → pass security
  • 11 Sept 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.

  • 9 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.

  • 7 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.

  • 5 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.

  • 2 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.

  • 31 Aug 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.

  • 29 Aug 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.

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 22 Sept 2026 · Probed https://mcp.takident.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=takident.com CN=YE2,O=Let's Encrypt,C=US 28 Jul 2026 26 Oct 2026 ECDSA 256 ECDSA-SHA384 52a91361fd41bf10c5c25535d034048c44b
SANs: *.takident.com, takident.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 mcp.takident.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
takident.com. present 2371 13 Verified
mcp.takident.com. Verified address RRset verified with the apex keys
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.takident.com/mcp Verified 200
http (plaintext) http://mcp.takident.com/mcp HTTPS enforced 301 https://mcp.takident.com/mcp
MCP tools · 12 exposed · ~776 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
fetch ~95

Retrieves the full published record for an entity returned by search (clinic, doctor, treatment, service or policy). Pass the value of the search result's `id` field — the parameter may be given as either `id` or `entity_id`.

NameTypeReqDescription
entity_idstringAlias for `id`, accepted for backward compatibility
idstringEntity id returned by search, e.g. doctor:sadik-taki
NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_aftercare_information ~33

Returns the clinic's remote follow-up schedule and the process for handling a suspected problem after a patient has returned home.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_clinic_profile ~40

Returns structured facts about the Taki Dent clinic: legal identity, address, contact details, languages spoken, and published certifications/licences/registrations.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_doctor_profile ~98

Returns a clinician profile — title, specialty, languages, education, and published professional memberships — matched by entity_id, full name, or a known name-spelling alias.

NameTypeReqDescription
doctorstringyesDoctor entity_id, name, alias, or page slug — "doctor:sadik-taki", "Dr. Sadık Taki", "Sadik Taki" and "dr-sadik-taki" all resolve to the same clinician.
NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_guarantee ~41

Returns the clinic's warranty terms, tiered by treatment material (implants, crowns, veneers, composite bonding), including exclusions and remote-claim process.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_prices ~48

Returns the clinic's published treatment prices in GBP and EUR, per treatment and per full-mouth package.

NameTypeReqDescription
treatmentstringOptional treatment id to filter, e.g. all-on-4
NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_reviews_summary ~28

Returns the clinic's Google review count and average rating, sourced from the live Google Business Profile.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_treatments ~24

Lists treatments offered by the clinic, each with its canonical page URL.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_visit_information ~38

Returns practical trip-planning facts: clinic location, opening hours, airport distance, transfers, accommodation, expected stay length, and package inclusions.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

get_whatsapp_contact ~59

Returns the clinic's WhatsApp contact deep link, pre-filled with a consultation-request message in the requested language.

NameTypeReqDescription
languagestringLanguage code (en, de, ar, tr, ru, fr, pl); defaults to en
NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

request_callback ~93

Requests a callback from the clinic's patient coordination team. Sends the provided name and contact details to the clinic (irreversible once sent). Collects only contact information; do not include medical details.

NameTypeReqDescription
consentbooleanyesUser confirms the clinic may contact them using these details.
emailstring
namestringyes
phonestring
preferred_languagestring
NameTypeReqDescription
detailstringyes
request_idstring
statusstringyes

No examples provided.

search ~179

Searches the clinic, doctor, treatment, service and policy entity index by name, alias, or summary text. Queries work in English, Turkish, German, Arabic, Russian, French and Polish. Each result carries an `id` that can be passed directly to the `fetch` tool.

NameTypeReqDescription
kindstringRestrict results to one entity kind. Omit to search every kind.
querystringyesFree-text search query in any of the seven site languages, e.g. "dental implant price", "implant fiyatı", "Zahnimplantat Preis", "цена импланта"
top_kintegerMaximum number of results to return (default 10, maximum 50). Results are ordered by relevance, so the first rows are the strongest matches. total_matches reports how many entities matched in total.
NameTypeReqDescription
dataobjectyes
evidencearrayyes
metaobjectyes

No examples provided.

Common questions

What is the com.takident/patient-services MCP server?

com.takident/patient-services is an MCP server listed in the public MCP registry as com.takident/patient-services. MCP server exposing structured data and tools for Taki Dent Patient Services (takident.com). This page covers its hosted endpoint (https://mcp.takident.com/mcp).

Is the com.takident/patient-services MCP server safe to use?

com.takident/patient-services 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 com.takident/patient-services MCP server expose?

com.takident/patient-services exposes 12 tools: fetch, get_aftercare_information, get_clinic_profile, get_doctor_profile, get_guarantee, and 7 more. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.

Does the com.takident/patient-services MCP server require authentication?

No. We connected to com.takident/patient-services without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.takident/patient-services MCP server still maintained?

com.takident/patient-services is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.