# Vascue Public Knowledge Search (remote · www.vascue.io)

Search Vascue's public healthcare-ops, insurance-claims and booking docs. Public content only.

- Trust score: 86/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `www.vascue.io`: 86/100 (this document), [markdown](https://verifymcp.io/servers/io-vascue-public-knowledge-search/mcp-search.md), [page](https://verifymcp.io/servers/io-vascue-public-knowledge-search/mcp-search)

## Channel facts

- Endpoint: `https://www.vascue.io/mcp/search`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 310 tokens (~310/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Vascue Public Knowledge Search MCP server?

Vascue Public Knowledge Search is a hosted endpoint at https://www.vascue.io/mcp/search, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-vascue-public-knowledge-search 'https://www.vascue.io/mcp/search'
```

### Cursor

```json
{
  "mcpServers": {
    "io-vascue-public-knowledge-search": {
      "url": "https://www.vascue.io/mcp/search"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-vascue-public-knowledge-search": {
      "type": "http",
      "url": "https://www.vascue.io/mcp/search"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-vascue-public-knowledge-search]
url = "https://www.vascue.io/mcp/search"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-vascue-public-knowledge-search": {
      "type": "remote",
      "url": "https://www.vascue.io/mcp/search",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-vascue-public-knowledge-search --url 'https://www.vascue.io/mcp/search' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-vascue-public-knowledge-search:
    url: "https://www.vascue.io/mcp/search"
```

### Netclaw

```json
{
  "McpServers": {
    "io-vascue-public-knowledge-search": {
      "Transport": "http",
      "Url": "https://www.vascue.io/mcp/search"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-vascue-public-knowledge-search -t streamable-http -u 'https://www.vascue.io/mcp/search'
```

### Other

```json
{
  "mcpServers": {
    "io-vascue-public-knowledge-search": {
      "type": "http",
      "url": "https://www.vascue.io/mcp/search"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `search` (~310 tokens)

Search Vascue's public documentation

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.

Input parameters:

- `ai_search_options` (object): Optional retrieval tuning. Omit for the defaults: hybrid search, 8 results, score threshold 0.35.
- `query` (string, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-vascue-public-knowledge-search/mcp-search#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 81
- 2026-09-08: 81
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 79
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 75
- 2026-08-26: 75
- 2026-08-25: 73
- 2026-08-24: 73
- 2026-08-23: 72

## Common questions

### What is the Vascue Public Knowledge Search MCP server?

Vascue Public Knowledge Search is an MCP server listed in the public MCP registry as io.vascue/public-knowledge-search. Search Vascue's public healthcare-ops, insurance-claims and booking docs. Public content only. This page covers its hosted endpoint (https://www.vascue.io/mcp/search).

### Is the Vascue Public Knowledge Search MCP server safe to use?

Vascue Public Knowledge Search scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Vascue Public Knowledge Search MCP server expose?

Vascue Public Knowledge Search exposes 1 tool: search. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.

### Does the Vascue Public Knowledge Search MCP server require authentication?

No. We connected to Vascue Public Knowledge Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Vascue Public Knowledge Search MCP server still maintained?

Vascue Public Knowledge Search is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.vascue.io/mcp/search
- Repository: https://github.com/vascue-io/public-knowledge-search
- Website: https://www.vascue.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-vascue-public-knowledge-search/mcp-search.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-vascue-public-knowledge-search/mcp-search.json
- HTML version of this page: https://verifymcp.io/servers/io-vascue-public-knowledge-search/mcp-search