VITALINK

chat.vitalinkv0.1.0Updated Oct 1, 2026

Find health professionals in 15 countries: public listings, verified credentials. No medical advice.

The publisher's own server: Vitalink

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant look up health professionals across 15 countries, with public listings and verified credentials.

What you can do
Search public listings of health professionals across 15 countries. Check verified credentials shown for listed practitioners. The manifest lists no individual tools, so the exact search and lookup operations are not documented. The service states it does not provide medical advice.
When to use it
Useful when you need to find or compare health practitioners in one of the covered countries and want to see their listed credentials. Not intended for medical advice or diagnosis.
Requirements
A remote MCP endpoint at mcp.vitalink.chat using streamable HTTP; no packages, environment variables or headers are declared. The manifest declares no authentication, though the provider's connect page may describe access conditions.
Before you install
Listings and credentials come from a third party, so verify them independently before relying on them. The service explicitly does not provide medical advice; do not treat results as clinical guidance. No authentication is declared, so consider what queries you send to the remote endpoint.

Installation

In SourceWeft

  1. Open VITALINK in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/chat.vitalink%2Fdirectory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vitalink": {
      "type": "http",
      "url": "https://mcp.vitalink.chat/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestOct 1, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Vitalink integrations