Vitalink MCP server
chat.vitalink/vitalinkvitalink.chatstreamable-httpv1.2.0Scanned
Talk to Vitalink's patient agent: surgery quotes from surgeons in Mexico for your case.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Vitalink MCP server can do
The Vitalink MCP server is published by vitalink.chat, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: talk_to_vitalink and talk_to_vitalink_with_account), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
talk_to_vitalinkEnvía el mensaje del paciente al agente de salud de VITALINK (México) y devuelve su respuesta en reply, para mostrarla al paciente.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Hablar con el agente de VITALINK
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
talk_to_vitalink_with_accountLo 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 (ped…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Hablar con el agente de VITALINK con tu cuenta
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.vitalink.chat/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://www.vitalink.chat
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.vitalink.chat/mcp: tools/list returned 2 tools to an anonymous client, including talk_to_vitalink (write), talk_to_vitalink_with_account (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vitalink https://mcp.vitalink.chat/mcpclaude mcp add --transport http vitalink https://mcp.vitalink.chat/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__vitalink__talk_to_vitalink",
"mcp__vitalink__talk_to_vitalink_with_account"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vitalink. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/chat.vitalink/vitalink/verify?hash=c0835e0b087830705aa96ec025edf78263d6c6f3b6d679f787d15e4c05345a60" | jq -e '.changed == false'Pinned hash c0835e0b0878, from Nov 11, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/chat.vitalink/vitalink/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/chat.vitalink/vitalink)Source: MCP Registry. Synced Nov 11, 2026, 03:17 UTC.
Vitalink MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vitalink MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Vitalink MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Vitalink MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Vitalink MCP server have?
- 2 tools: 2 write. talk_to_vitalink and talk_to_vitalink_with_account.
Does the Vitalink MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Vitalink MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Vitalink MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.