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.

Vitalink

REMOTE · MCP.VITALINK.CHAT

Talk to Vitalink's patient agent: surgery quotes from surgeons in Mexico for your case.

+3 this week 76 Trust /100

Last scanned (21 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 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 Security80
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 717 tokens (~358/item across 2 items; 2 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 Management33
  • Stability observed for 10 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 71

    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 21 Nov 2026 · Probed https://mcp.vitalink.chat/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.vitalink.chat CN=YR1,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 RSA 2048 SHA256-RSA 678eb80cd589ea3731b7c3379450b1d7fce
SANs: mcp.vitalink.chat
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.vitalink.chat. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
chat. DS published 33026 8 Verified
vitalink.chat. No DS 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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.vitalink.chat/mcp Verified 200
http (plaintext) http://mcp.vitalink.chat/mcp HTTPS enforced 308 https://mcp.vitalink.chat/mcp
MCP tools · 2 exposed · ~420 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
talk_to_vitalink ~213

Envía el mensaje del paciente al agente de salud de VITALINK (México) y devuelve su respuesta en reply, para mostrarla al paciente. El agente explica el servicio de cotizaciones de cirugía y conversa sobre el procedimiento que el paciente quiere cotizar, su zona y sus fechas; no diagnostica ni da precios. VITALINK guarda la conversación para trazabilidad y calidad; conversation se envía de vuelta en la siguiente llamada. Si lo que pide el paciente necesita su cuenta, devuelve needsAccount: true.

NameTypeReqDescription
conversationstring–Token opaco de la respuesta anterior (conversation), sin cambiarlo; omítelo al empezar. No contiene nada que la app deba leer.
messagestringyesEl mensaje del paciente para el agente de VITALINK sobre lo que quiere cotizar o consultar (procedimiento, zona, fechas, dudas). No incluyas su nombre completo, teléfono, correo, dirección ni números…

No output schema declared.

No examples provided.

talk_to_vitalink_with_account ~207

Lo mismo que talk_to_vitalink, con la cuenta de VITALINK del paciente conectada: el agente usa su conversación, sus solicitudes y sus cotizaciones, y puede preparar una acción (pedir cotizaciones, una cita o aceptar una cotización). Preparar no ejecuta nada: el agente le manda al paciente la confirmación exacta por WhatsApp y solo se hace si contesta que sí ahí. Al conectar, la conversación de conversation pasa a su cuenta.

NameTypeReqDescription
conversationstring–Token opaco de la respuesta anterior (conversation), sin cambiarlo; omítelo al empezar. No contiene nada que la app deba leer.
messagestring–El mensaje del paciente para el agente de VITALINK sobre lo que quiere cotizar o consultar (procedimiento, zona, fechas, dudas). No incluyas su nombre completo, teléfono, correo, dirección ni números…

No output schema declared.

No examples provided.

Install

How do I install the Vitalink MCP server?

Vitalink is a hosted endpoint at https://mcp.vitalink.chat/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.vitalink.chat

# add to Claude Code
claude mcp add --transport http chat-vitalink-vitalink 'https://mcp.vitalink.chat/mcp'
Common questions

What is the Vitalink MCP server?

Vitalink is an MCP server listed in the public MCP registry as chat.vitalink/vitalink. Talk to Vitalink's patient agent: surgery quotes from surgeons in Mexico for your case. This page covers its hosted endpoint (https://mcp.vitalink.chat/mcp).

Is the Vitalink MCP server safe to use?

Vitalink scores 76 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 Vitalink MCP server expose?

Vitalink exposes 2 tools: talk_to_vitalink, talk_to_vitalink_with_account. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.

Does the Vitalink MCP server require authentication?

No. We connected to Vitalink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vitalink MCP server still maintained?

Vitalink is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Vitalink MCP server?

VerifyMCP ran 13 checks on Vitalink, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.