Root Data Public Directory
REMOTE · ROOTDATA.AI · SCANNED SEP 27
Public Root Data dental analytics directory for DSOs, dental practices, blog, and FAQ tools.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 491 tokens (~61/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Root Data Public Directory MCP server?
Root Data Public Directory is a hosted endpoint at https://rootdata.ai/api/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.
remote · rootdata.ai
claude mcp add --transport http ai-rootdata-public-directory 'https://rootdata.ai/api/mcp'
{
"mcpServers": {
"ai-rootdata-public-directory": {
"url": "https://rootdata.ai/api/mcp"
}
}
} {
"servers": {
"ai-rootdata-public-directory": {
"type": "http",
"url": "https://rootdata.ai/api/mcp"
}
}
} [mcp_servers.ai-rootdata-public-directory] url = "https://rootdata.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-rootdata-public-directory": {
"type": "remote",
"url": "https://rootdata.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-rootdata-public-directory --url 'https://rootdata.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-rootdata-public-directory:
url: "https://rootdata.ai/api/mcp" {
"McpServers": {
"ai-rootdata-public-directory": {
"Transport": "http",
"Url": "https://rootdata.ai/api/mcp"
}
}
} assistant mcp add ai-rootdata-public-directory -t streamable-http -u 'https://rootdata.ai/api/mcp'
{
"mcpServers": {
"ai-rootdata-public-directory": {
"type": "http",
"url": "https://rootdata.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://rootdata.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rootdata.ai | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 13 Jun 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 20e71e2307f8740912c09f1a316cbed |
| SANs: rootdata.ai | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rootdata.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| rootdata.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-ee96d60877f5442b889e41dca1f536b3' 'strict-dynamic' https: http:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' blob: https:; worker-src 'self' blob:; frame-src 'self' https:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rootdata.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://rootdata.ai/api/mcp | HTTPS enforced | 301 | https://rootdata.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_dsos Compare DSOs ~54
Compare two Root Data public DSO directory profiles by slug using public profile summaries, regions, websites, and public signal counts.
| Name | Type | Req | Description |
|---|---|---|---|
| dso_slug1 | string | yes | – |
| dso_slug2 | string | yes | – |
No output schema declared.
No examples provided.
get_dso_profile Get DSO Profile ~44
Get one public Root Data DSO directory profile by slug. Returns public website, region, profile URL, summary, and public signals.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_practice_profile Get Practice Profile ~43
Get one published public dental practice directory profile by slug. Returns public website, locations, services, rating summary, and profile URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_top_dsos List Top DSOs ~56
List public DSO directory profiles ranked by public size, locations, or growth signals inferred from public profile text. Results are directional, not a private operating benchmark.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
root_data_faq Root Data FAQ ~53
Answer common public questions about Root Data services, DSO directories, dental practice benchmarks, AI Coach, integrations, privacy, demos, and pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
search_blog_articles Search Blog Articles ~67
Search published Root Data blog articles by title, slug, excerpt, category, tag, or SEO summary. Supports DSO-only, practice-only, both-audience, or all articles.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
search_dsos Search DSOs ~52
Search Root Data's public DSO directory by organization name, slug, website, summary, or public website signals. Returns public directory data only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
search_practices Search Dental Practices ~122
Search Root Data's public dental practice directory. Supports query, service, location, city, state, minimum Google reviews, minimum star rating, and sorting by Google review count or rating. Returns published public listings only. All parameters are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| limit | integer | – | – |
| location | string | – | – |
| query | string | – | – |
| reviews | integer | – | – |
| service | string | – | – |
| sortBy | string | – | – |
| stars | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
What is the Root Data Public Directory MCP server?
Root Data Public Directory is an MCP server listed in the public MCP registry as ai.rootdata/public-directory. Public Root Data dental analytics directory for DSOs, dental practices, blog, and FAQ tools. This page covers its hosted endpoint (https://rootdata.ai/api/mcp).
Is the Root Data Public Directory MCP server safe to use?
Root Data Public Directory scores 73 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 Root Data Public Directory MCP server expose?
Root Data Public Directory exposes 8 tools: search_dsos, get_dso_profile, search_practices, get_practice_profile, list_top_dsos, and 3 more. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.
Does the Root Data Public Directory MCP server require authentication?
No. We connected to Root Data Public Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Root Data Public Directory MCP server still maintained?
Root Data Public Directory is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.