Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Root Data Public Directory

REMOTE · ROOTDATA.AI · SCANNED AUG 3

Public Root Data dental analytics directory for DSOs, dental practices, blog, and FAQ tools.

Available components

+5 this week 61 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · rootdata.ai

# add to Claude Code
claude mcp add --transport http ai-rootdata-public-directory https://rootdata.ai/api/mcp
# ~/.codex/config.toml
[mcp_servers.ai-rootdata-public-directory]
url = "https://rootdata.ai/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-rootdata-public-directory": {
      "type": "remote",
      "url": "https://rootdata.ai/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-rootdata-public-directory --url https://rootdata.ai/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-rootdata-public-directory:
    url: "https://rootdata.ai/api/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 2 Aug 26 +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.

  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

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

  • 29 Jul 26 +1

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

  • 27 Jul 26 +1
    • 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 55

    First indexed and scored.

Diagnostics

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 3 Aug 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
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
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
MCP tools — 8 exposed · ~491 tokens

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.

Tool Tokens
compare_dsos ~54

Compare two Root Data public DSO directory profiles by slug using public profile summaries, regions, websites, and public signal counts.

NameTypeReqDescription
dso_slug1stringyes
dso_slug2stringyes

No output schema declared.

No examples provided.

get_dso_profile ~44

Get one public Root Data DSO directory profile by slug. Returns public website, region, profile URL, summary, and public signals.

NameTypeReqDescription
slugstringyes

No output schema declared.

No examples provided.

get_practice_profile ~43

Get one published public dental practice directory profile by slug. Returns public website, locations, services, rating summary, and profile URL.

NameTypeReqDescription
slugstringyes

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
bystringyes
limitinteger

No output schema declared.

No examples provided.

root_data_faq ~53

Answer common public questions about Root Data services, DSO directories, dental practice benchmarks, AI Coach, integrations, privacy, demos, and pricing.

NameTypeReqDescription
limitinteger
querystring

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
audiencestring
limitinteger
querystring

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
limitinteger
querystring

No output schema declared.

No examples provided.

search_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.

NameTypeReqDescription
citystring
limitinteger
locationstring
querystring
reviewsinteger
servicestring
sortBystring
starsnumber
statestring

No output schema declared.

No examples provided.