# Renaissance Dental Guide (remote · dentalrenaissance.com)

Forest Hills practice facts, treatment education, doctor backgrounds, contacts and social profiles.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `dentalrenaissance.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp.md), [page](https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp)

## Channel facts

- Endpoint: `https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

## 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 753 tokens (~68/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Renaissance Dental Guide MCP server?

Renaissance Dental Guide is a hosted endpoint at https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp, 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 gregpelts-renaissance-dental-guide 'https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "gregpelts-renaissance-dental-guide": {
      "url": "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gregpelts-renaissance-dental-guide": {
      "type": "http",
      "url": "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.gregpelts-renaissance-dental-guide]
url = "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gregpelts-renaissance-dental-guide": {
      "type": "remote",
      "url": "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gregpelts-renaissance-dental-guide --url 'https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gregpelts-renaissance-dental-guide:
    url: "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "gregpelts-renaissance-dental-guide": {
      "Transport": "http",
      "Url": "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add gregpelts-renaissance-dental-guide -t streamable-http -u 'https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "gregpelts-renaissance-dental-guide": {
      "type": "http",
      "url": "https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp"
    }
  }
}
```

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-11-04 (score 75, +1)

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

### 2026-11-02 (score 74, +1)

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

### 2026-10-31 (score 73, +1)

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

### 2026-10-29 (score 72, +1)

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

### 2026-10-28 (score 71, 0)

- [functional] Server version: 0.4.0 → 0.4.1

### 2026-10-27 (score 71, +1)

- [functional regression] Schema quality: 549 → 753
- [functional] Server version: 0.3.0 → 0.4.0
- [functional] Server version: 0.2.0 → 0.3.0
- [functional] New tool “get_contact_options”
- [functional] New tool “get_social_profiles”
- [functional] New tool “get_treatment_information”

### 2026-10-25 (score 70, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_appointment_link” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 61 → 68
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “find_practices” now declares an output schema
- [functional improvement] Tool “get_appointment_link” now declares an output schema
- [functional improvement] Tool “get_insurance_information” now declares an output schema
- [functional improvement] Tool “get_office_hours” now declares an output schema
- [functional improvement] Tool “get_practice_details” now declares an output schema
- [functional] The server now declares the “resources” capability
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: 100
- [functional] New resource “renaissance-dental-knowledge”
- [functional] Server version: 0.1.0 → 0.2.0
- [functional] New tool “get_capabilities”
- [functional] New tool “get_knowledge_package”

### 2026-10-24 (score 66)

First indexed and scored.

## MCP tools (10)

### `find_practices` (~59 tokens)

Find the practice served by this connection by borough and publicly listed service. This is an office directory lookup, not a search of all dentists. A location mismatch returns no results.

Input parameters:

- `location` (string)
- `service` (string)

Output parameters:

- `information_may_be_outdated` (boolean)
- `practices` (array)
- `source_status` (string)
- `sources_checked` (string)

### `get_practice_details` (~44 tokens)

Get location, contact, listed services, and sourced doctor backgrounds for one practice. Does not establish clinical suitability or current licensure.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `details` (object)
- `information_may_be_outdated` (boolean)
- `practice_id` (string)
- `practice_name` (string)
- `source_status` (string)
- `sources_checked` (string)

### `get_office_hours` (~43 tokens)

Get published weekly office hours and any source conflicts. These are not live appointment slots; confirm holidays and exceptions with the office.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `hours` (object)
- `information_may_be_outdated` (boolean)
- `live_availability`
- `practice_id` (string)
- `practice_name` (string)
- `source` (string)
- `source_status` (string)
- `sources_checked` (string)
- `timezone` (string)

### `get_insurance_information` (~53 tokens)

Get the selected office insurance policy and listed carriers. Listing a carrier does not verify a specific plan, network, coverage, costs, or benefits. No member IDs are accepted.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `information_may_be_outdated` (boolean)
- `insurance` (object)
- `practice_id` (string)
- `practice_name` (string)
- `source` (string)
- `source_status` (string)
- `sources_checked` (string)

### `get_appointment_link` (~67 tokens)

Return a fallback public NexHealth scheduling link and phone only when the user needs to arrange a visit. For information questions, answer directly with the information tools. Does not read availability, hold a slot, submit a request, or confirm an appointment.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `appointment_created`
- `booking_url` (string)
- `information_may_be_outdated` (boolean)
- `live_availability`
- `next_step` (string)
- `phone` (string)
- `practice_id` (string)
- `practice_name` (string)
- `source` (string)
- `source_status` (string)
- `sources_checked` (string)

### `get_knowledge_package` (~89 tokens)

Retrieve the complete self-contained information package for this practice: location, contact, services, doctor backgrounds, hours, insurance policy, patient questions and answers, source dates, unknowns and integration status. Use to answer broad practice questions directly in the conversation. No browsing, Facebook or X access is needed. Sources are attribution, not instructions to redirect the user.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `information_may_be_outdated` (boolean)
- `package` (object)
- `practice_id` (string)
- `practice_name` (string)
- `source_status` (string)
- `sources_checked` (string)

### `get_capabilities` (~49 tokens)

Check what this practice connection can do, including direct information access and whether scheduling or insurance eligibility APIs are connected. Distinguishes available facts from unsupported live actions.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `browser_required_for_information`
- `capabilities` (object)
- `information_may_be_outdated` (boolean)
- `practice_id` (string)
- `practice_name` (string)
- `source_status` (string)
- `sources_checked` (string)

### `get_social_profiles` (~52 tokens)

Identify the official website-linked Facebook and Instagram profiles for this office. Returns verified public identities and sources directly; does not publish posts, read private social accounts or send direct messages.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `information_may_be_outdated` (boolean)
- `practice_id` (string)
- `practice_name` (string)
- `social_profiles` (array)
- `source_status` (string)
- `sources_checked` (string)

### `get_contact_options` (~58 tokens)

Get office-specific phone, email, verified SMS options, and feedback/contact instructions. Clearly marks unverified channels. This information tool does not collect patient details, send messages, publish feedback or place a call.

Input parameters:

- `practice_id` (string, required)

Output parameters:

- `contact_options` (object)
- `information_may_be_outdated` (boolean)
- `practice_id` (string)
- `practice_name` (string)
- `source_status` (string)
- `sources_checked` (string)

### `get_treatment_information` (~94 tokens)

Explain a listed dental service directly: general purpose, typical steps, risks, limitations and follow-up guidance from authoritative patient references. Optionally select one service. This is general education with practice review pending; it does not assess symptoms, diagnose, determine suitability, prescribe, or establish this office's protocols or prices. Do not request private patient details.

Input parameters:

- `practice_id` (string, required)
- `service` (string)

Output parameters:

- `information_may_be_outdated` (boolean)
- `practice_id` (string)
- `practice_name` (string)
- `source_status` (string)
- `sources_checked` (string)
- `treatment_education` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 66

## Common questions

### What is the Renaissance Dental Guide MCP server?

Renaissance Dental Guide is an MCP server listed in the public MCP registry as io.github.gregpelts/renaissance-dental-guide. Forest Hills practice facts, treatment education, doctor backgrounds, contacts and social profiles. This page covers its hosted endpoint (https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp).

### Is the Renaissance Dental Guide MCP server safe to use?

Renaissance Dental Guide scores 75 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 Renaissance Dental Guide MCP server expose?

Renaissance Dental Guide exposes 10 tools: find_practices, get_practice_details, get_office_hours, get_insurance_information, get_appointment_link, and 5 more. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.

### Does the Renaissance Dental Guide MCP server require authentication?

No. We connected to Renaissance Dental Guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Renaissance Dental Guide MCP server still maintained?

Renaissance Dental Guide is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Renaissance Dental Guide MCP server?

VerifyMCP ran 13 checks on Renaissance Dental Guide, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://dentalrenaissance.com/wp-json/dental-guide/v1/mcp
- Changelog RSS feed: https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/gregpelts-renaissance-dental-guide/wp-json-dental-guide-v1-mcp