Vascue Public Knowledge Search (MCP server)

MCP serverSearch

Your AI can search Vascue's public documentation on healthcare operations, insurance claims, and booking. Once added, you can ask a question and it will look up the relevant public docs for you. Only publicly available content is included.

Use Vascue Public Knowledge Search (MCP server) in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Vascue Public Knowledge Search (MCP server) and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use Vascue Public Knowledge Search (MCP server) to search

Details

Available today. Use it from your connected AI after setup.

After adding it, ask your AI a question about healthcare operations, insurance claims, or booking and let it search Vascue's public docs for the answer.

Vascue Public Knowledge Search (MCP server)Start free

What your AI can do with it

  • Search Vascue's public healthcare operations docs
  • Look up insurance claims documentation
  • Find answers in Vascue's booking docs
  • Pull details from public documentation when you ask a question

Install Vascue Public Knowledge Search (MCP server)

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user vascue-public-knowledge-search-m 'https://www.vascue.io/mcp/search'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://www.vascue.io/mcp/search

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=vascue-public-knowledge-search-m&config=eyJ1cmwiOiJodHRwczovL3d3dy52YXNjdWUuaW8vbWNwL3NlYXJjaCJ9

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://www.vascue.io/mcp/search

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add vascue-public-knowledge-search-m --url 'https://www.vascue.io/mcp/search'

    Run it once, then sign in with codex mcp login vascue-public-knowledge-search-m if the server asks for an account.

From the project's README

As published by vascue-io/public-knowledge-search in README.md.

A Model Context Protocol server that searches Vascue's public documentation: healthcare operations, the AI front desk for clinics, provider-side insurance claims automation, Cliniko integration, security, case studies and pricing.

It comes in two equivalent forms:

  • Hosted (always current): https://www.vascue.io/mcp/search - streamable HTTP, no authentication.

  • Self-contained (this repo): python server.py - local BM25 search over a bundled snapshot of the public pages (content/, refreshed per release with scripts/fetch_content.py). No network calls at runtime, so it also works offline and is what directory-built releases run.

  • Endpoint: https://www.vascue.io/mcp/search (streamable HTTP, no authentication)

  • Server card: https://www.vascue.io/.well-known/mcp/server-card.json

  • Registry name: io.vascue/public-knowledge-search

  • Operated by: Vascue Limited (ISO 27001 certified)

Public content only. This server indexes public product and educational pages. Never send patient information, claim documents, clinic credentials or booking requests to it. Agent-based clinic booking is a separate research pilot, not a public API.

Connect

Any MCP client that speaks streamable HTTP can connect to the endpoint directly.

Claude Code

claude mcp add --transport http vascue-search https://www.vascue.io/mcp/search

Cursor / Claude Desktop / other stdio-only clients (via mcp-remote)

{
  "mcpServers": {
    "vascue-search": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.vascue.io/mcp/search"]
    }
  }
}

Self-contained local server (stdio; bundled snapshot, no network)

pip install -r requirements.txt
python server.py

Docker (builds the self-contained server)

docker build -t vascue-public-knowledge-search .
docker run -i --rm vascue-public-knowledge-search

Tools

One tool, no authentication, read-only.

search

Hybrid (keyword + vector) search over Vascue's public pages. Returns matching excerpts with their canonical https://www.vascue.io/... URLs so answers can cite the source.

InputTypeNotes
querystring (required)Natural-language question or keywords, e.g. "how does Vascue handle insurance claim pre-authorisation".
ai_search_options.retrieval.retrieval_type"hybrid" | "vector" | "keyword"Default hybrid.
ai_search_options.retrieval.max_num_resultsinteger 1–50Default 8.
ai_search_options.retrieval.match_thresholdnumber 0–1Default 0.35.
ai_search_options.retrieval.context_expansioninteger 0–3Neighbouring chunks to include.

Query rewriting and reranking are disabled server-side; the server returns source chunks only and never a generated answer, so nothing is presented as a Vascue statement without a citation. Rate limit: 60 requests per minute per client.

Example call:

{ "name": "search", "arguments": { "query": "Cliniko integration for AI front desk" } }

The endpoint is backed by a Cloudflare AI Search instance over the approved public Markdown export of vascue.io (the service descriptor at https://www.vascue.io/.well-known/ai-search.json states what is and is not indexed).

Development

docker build -t vascue-public-knowledge-search .
node scripts/smoke.mjs docker run -i --rm vascue-public-knowledge-search   # initialize -> tools/list
node scripts/smoke.mjs npx -y mcp-remote https://www.vascue.io/mcp/search --transport http-only

CI runs the same build and smoke test on every push and weekly, so the badge above doubles as an endpoint health indicator.

Directory build specs

Directories that build the server from source (e.g. Glama) run the self-contained form. Generated build images vary (uv-managed Python without pip, or a PEP 668 externally-managed system Python), so use an explicit venv:

  • Build steps: ["uv venv /opt/venv && uv pip install --python /opt/venv/bin/python -r requirements.txt"]
  • CMD: ["/opt/venv/bin/python", "server.py"]
  • No environment variables.

Where a normal pip exists, plain pip install -r requirements.txt + ["python", "server.py"] works too.

pip install -r requirements.txt
SMOKE_CALL_QUERY="Cliniko integration" node scripts/smoke.mjs python server.py   # local server
node scripts/smoke.mjs python bridge.py                                          # stdio bridge to the hosted endpoint
python scripts/fetch_content.py                                                  # refresh the content/ snapshot

Other machine-readable surfaces

  • https://www.vascue.io/llms.txt
  • https://www.vascue.io/openapi.json (public, read-only content API)
  • https://www.vascue.io/.well-known/agent-skills/index.json (agent skills; also at vascue-io/skills)

Licence

This repository (README, manifest, Dockerfile) is MIT licensed. The content served by the endpoint is Vascue's public website content.

Tools it offers (1)

What this server listed when Ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • search

Signals

Last commit
Aug 2026
Advanced
Delivery
public-knowledge-search MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
io-vascue-public-knowledge-search
Source
github.com/vascue-io/public-knowledge-search
Hosted endpoint
https://www.vascue.io/mcp/search