A
licenseNot graded
qualityD
maintenanceAccess any documentation indexed by RagRabbit Open Source AI site search
15
135
MIT
Vascue Public Knowledge Search
by io.vascue
Server Details
Search Vascue's public healthcare-ops, insurance-claims and booking docs. Public content only.
Ownership verified
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- vascue-io/public-knowledge-search
- GitHub Stars
- 0
- Server Listing
- Vascue Public Knowledge Search
Available Tools
1 toolsearchSearch Vascue's public documentationARead-onlyIdempotentInspect
Hybrid keyword + semantic search over the public pages of vascue.io: 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 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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | What to look for, as a natural-language question or keywords, e.g. "how does claims pre-authorisation work" or "Cliniko integration". 3-15 words works best; one topic per call. | |
| ai_search_options | No | Optional retrieval tuning. Omit for the defaults: hybrid search, 8 results, score threshold 0.35. |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes well beyond the annotations by disclosing rate limits (60 requests per minute per client), no authentication, read-only and idempotent behavior, and content restrictions. It also warns that off-topic queries still return nearest chunks and that low scores are weak evidence. This is strong behavioral context that helps the agent set expectations and respond honestly.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but well organized: capabilities first, usage rules next, response shape, then safety boundaries. Every sentence adds information needed for correct invocation or interpretation, with no filler or tautology.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having no output schema, the description fully compensates by detailing the response shape (result.chunks[] with text, score, item.metadata.url) and expected behavior on low scores. With rich parameter schema plus this description, the agent has everything needed to invoke the tool and interpret results correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents the query and ai_search_options parameters thoroughly, including retrieval types, thresholds, and defaults. The description adds usage nuance such as 'one topic per call' and the 0.5 score interpretation, but those overlap with schema guidance and do not substantially improve parameter understanding beyond it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as hybrid keyword + semantic search over Vascue's public documentation, enumerating the exact content areas (healthcare-operations guides, integrations, security pages, blog posts, etc.). It also gives the intended use — answering questions about Vascue's products and published content — which fully distinguishes the tool's purpose even without siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states when to use the tool: to answer questions about what Vascue offers and how products work. It also spells out usage constraints: one topic per call, cite returned page URLs for every excerpt, treat scores below about 0.5 as weak evidence, and avoid sending patient information or clinic credentials. The closing boundary — cannot book appointments or look up clinic data — prevents misuse.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
search15 fields changed- removed
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#" - changed
Input schema / properties / ai_search_options / descriptionPrevious value: -"Options for customizing the AI search behavior."New value: +"Optional retrieval tuning. Omit for the defaults: hybrid search, 8 results, score threshold 0.35." - removed
Input schema / properties / ai_search_options / properties / cacheRemoved value: -{ - "properties": { - "cache_threshold": { - "type": "string" - }, - "enabled": { - "type": "boolean" - } - }, - "type": "object" -} - removed
Input schema / properties / ai_search_options / properties / query_rewriteRemoved value: -{ - "properties": { - "enabled": { - "const": false, - "type": "boolean" - }, - "rewrite_prompt": { - "type": "string" - } - }, - "type": "object" -} - removed
Input schema / properties / ai_search_options / properties / rerankingRemoved value: -{ - "properties": { - "enabled": { - "const": false, - "type": "boolean" - }, - "match_threshold": { - "maximum": 1, - "minimum": 0, - "type": "number" - } - }, - "type": "object" -} - added
Input schema / properties / ai_search_options / properties / retrieval / properties / context_expansion / descriptionAdded value: +"Neighbouring chunks from the same page to include around each hit (default 0)." - removed
Input schema / properties / ai_search_options / properties / retrieval / properties / filtersRemoved value: -{ - "additionalProperties": { - "anyOf": [ - { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - { - "properties": { - "$eq": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "$gt": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - } - ] - }, - "$gte": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - } - ] - }, - "$in": { - "items": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "type": "array" - }, - "$lt": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - } - ] - }, - "$lte": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - } - ] - }, - "$ne": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "$nin": { - "items": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ] - }, - "type": "array" - } - }, - "type": "object" - } - ] - }, - "propertyNames": { - "type": "string" - }, - "type": "object" -} - removed
Input schema / properties / ai_search_options / properties / retrieval / properties / fusion_methodRemoved value: -{ - "enum": [ - "max", - "rrf" - ], - "type": "string" -} - added
Input schema / properties / ai_search_options / properties / retrieval / properties / match_threshold / descriptionAdded value: +"Minimum relevance score for a chunk to be included (default 0.35); raise for precision, lower for recall." - added
Input schema / properties / ai_search_options / properties / retrieval / properties / max_num_results / descriptionAdded value: +"Maximum chunks to return (default 8)." - removed
Input schema / properties / ai_search_options / properties / retrieval / properties / metadata_onlyRemoved value: -{ - "type": "boolean" -} - added
Input schema / properties / ai_search_options / properties / retrieval / properties / retrieval_type / descriptionAdded value: +"hybrid (default) fuses keyword and vector ranking; keyword for exact phrases or product names; vector for paraphrased questions." - changed
Input schema / properties / ai_search_options / properties / retrieval / properties / retrieval_type / enumPrevious value: -[ - "vector", - "keyword", - "hybrid" -]New value: +[ + "hybrid", + "vector", + "keyword" +] - removed
Input schema / properties / ai_search_options / properties / retrieval / properties / return_on_failureRemoved value: -{ - "type": "boolean" -} - changed
Input schema / properties / query / descriptionPrevious value: -"The input query."New value: +"What to look for, as a natural-language question or keywords, e.g. \"how does claims pre-authorisation work\" or \"Cliniko integration\". 3-15 words works best; one topic per call."
1 tool update
- First observed
search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Search and fetch AgendaForge public documentation and marketing content. No authentication needed.
Search and read the public Applivery docs (MDM & app distribution). Read-only, no auth.
Read-only search and page retrieval from the public Atisbo documentation corpus. No authentication.
Search SORACOM documentation: service guides, FAQ, API references, IoT recipes, etc.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables searching medical literature, clinical trials, drug information, guidelines, and medical fee schedules directly from Claude, returning only original sources and text without medical judgment.9MIT
- AlicenseAqualityDmaintenanceSearch and fetch MCP protocol documentation using BM25 search with weighted scoring and stemming.2482MIT
- FlicenseAqualityCmaintenanceEnables MCP clients to retrieve authoritative AI Square documentation, API references, SDK examples, guides, and troubleshooting information through citation-safe hybrid search and static resources.11-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
With only one tool, there is no possibility of confusing it with another. The single 'search' tool has a clearly defined purpose.
Naming Consistency4/5
The lone tool is named 'search', which is simple and clear. Naming consistency is hard to evaluate with one tool, but the name aligns with its function and common conventions.
Tool Count3/5
A single dedicated search tool fits the server's stated read-only knowledge-search purpose, but it is minimal. One tool can feel thin, though it is justifiable for a focused search endpoint.
Completeness3/5
The search tool covers a broad range of public pages (guides, product info, integrations, security, case studies, pricing, blog), but there are no additional tools for filtering, retrieving specific pages, or understanding the corpus structure. The surface is functionally complete for simple Q&A but lacks depth for complex discovery workflows.