Vascue Public Knowledge Search
OfficialThis server performs keyword search over a bundled snapshot of Vascue's public documentation, returning citable excerpts.
Search public Vascue docs with one tool,
search, using a natural-language query or keywords (3–15 words, one topic per call).Limit results via
max_num_results(1–50, default 8).Get citable excerpts: returns
{"chunks": [...]}ranked by relevance, each withurl(canonical vascue.io page),title,score(0–1 relative to best match) andtext(Markdown excerpt).Coverage: healthcare-operations guides, AI front desk, insurance-claims automation, Cliniko/Nookal integrations, security and compliance, case studies, pricing and blog posts.
Runs fully locally: read-only, idempotent, no network calls, no authentication; empty results mean the snapshot lacks the topic (say so rather than guess).
Limitations: public content only — never send patient info, claim documents, clinic credentials or booking requests; it cannot book appointments or look up clinic data.
Freshness note: the index is a point-in-time copy;
https://www.vascue.io/mcp/searchis the always-current hosted twin.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Vascue Public Knowledge Search (MCP server)
A Model Context Protocol server that searches Vascue's public documentation: healthcare operations, Vascue Front Desk for clinics, provider-side insurance claims automation, practice-management integrations (two-way sync with Cliniko and Nookal; Jane, Mindbody, PracticeHub, HexaHealth, Halaxy, Clinicea, ClinicOffice, Semble, Plato Medical and JERA in progress), 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 withscripts/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-searchOperated 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/searchCursor / 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.pyDocker (builds the self-contained server)
docker build -t vascue-public-knowledge-search .
docker run -i --rm vascue-public-knowledge-searchRelated MCP server: Cliniko MCP Server
Tools
One tool, search, in both forms: no authentication, read-only. The inputs differ between the hosted endpoint and the local server.
Hosted endpoint (https://www.vascue.io/mcp/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.
Input | Type | Notes |
|
| Natural-language question or keywords, e.g. "how does Vascue handle insurance claim pre-authorisation". |
|
| Default hybrid. |
|
| Default 8. |
|
| Default 0.35. |
|
| Neighbouring 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 Vascue 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).
Local server (server.py)
BM25 keyword search over the bundled content/ snapshot. No network calls at runtime. Returns {"chunks": [...]}, each chunk with url, title, score (0–1, relative to the best match) and text.
Input | Type | Notes |
|
| Natural-language question or keywords; 3–15 words, one topic per call. |
|
| Default 8. |
Example call:
{ "name": "search", "arguments": { "query": "Cliniko integration", "max_num_results": 5 } }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-onlyCI 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/ snapshotOther machine-readable surfaces
https://www.vascue.io/llms.txthttps://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.
Available Tools
1 toolsearchSearch Vascue's public documentationARead-onlyIdempotentInspect
Keyword (BM25) search over a bundled snapshot of vascue.io's public pages: healthcare-operations guides, the AI front desk for clinics, provider-side insurance-claims automation, Cliniko and Nookal integration, security and compliance pages, case studies, pricing and blog posts.
Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use.
Returns {"chunks": [...]} ordered by relevance; each chunk has url (the canonical https://www.vascue.io/... page), title, score (0-1 relative to the best match) and text (a Markdown excerpt). An empty list means the snapshot does not mention the topic - say so rather than guessing. The index is a point-in-time copy of the public site; https://www.vascue.io/mcp/search is the always-current hosted twin.
Runs fully locally: read-only, idempotent, no network calls, no authentication. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.
Inputs: query (required), max_num_results. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusion between tools. The 'search' tool's purpose is unambiguous and clearly scoped to a specific domain (Vascue public knowledge).
The single tool is named 'search', which is a simple, clear verb that perfectly matches its function. There is no inconsistency to evaluate, and the name is intuitive.
The server provides exactly one tool, which is slightly below the typical 3-15 tool range. However, given the narrow purpose of 'Public Knowledge Search', a single search tool is well-scoped and earns its place, making the count appropriate.
The tool covers the entire domain of knowledge search for Vascue's public pages, including search, relevance ranking, and citation of sources. There are no obvious missing operations for its stated purpose; it is a complete, focused toolkit.
Maintenance
Related MCP Connectors
Search the Amomic-AI docs and REST API for AI agents on calls, WhatsApp, chat and email.
Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.
Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.
Search the SiteGPT documentation: setup, features, API reference, troubleshooting.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing AI assistants with access to healthcare data tools, including FDA drug information, PubMed research, health topics, clinical trials, and medical terminology lookup.736 npm131MIT
- FlicenseNot gradedqualityDmaintenanceEnables integration with the Cliniko practice management system through MCP tools and resources. Supports patient management, appointment scheduling, and practice data access through natural language interactions.-
- AlicenseBqualityDmaintenanceProvides comprehensive integration with the Cliniko API for healthcare practice management, including patient, appointment, and invoice administration. It enables tools for complex clinical workflows and direct access to practice resources through the Model Context Protocol.272MIT
- AlicenseBqualityDmaintenanceProvides integration with the Cliniko API for healthcare practice management, enabling patient, appointment, invoice, and payment operations via natural language.27MIT