Search Vascue's public healthcare-operations, insurance-claims and clinic-booking documentation. Public content only; never send patient data, credentials or booking requests.
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its description clearly bounds it to read-only hybrid search over vascue.io public pages, with explicit exclusions (no booking, no clinic data).
A single tool named 'search' is unambiguous and readable, though it is a bare verb with no resource qualifier (e.g. search_pages). With one tool there is no convention to violate, so this is close to ideal by default.
The server's stated purpose is a single capability — public knowledge search — so one tool is well-scoped rather than a gap. It sits at the low end of the typical 3-15 range, but adding more tools would be artificial here.
For a read-only public-content lookup service, a relevance-ranked search returning text, score, and canonical URL covers the lifecycle (query → excerpts → citation). Deliberate exclusions (booking, patient/claim/credential data) are documented limitations, not omissions.
Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, 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 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 a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic.
Read-only and idempotent; no authentication; 60 requests per minute per client. 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), ai_search_options.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.