General Tools

dentaldigitalcenter.com

Provides information about a Buenos Aires dental clinic, including treatments, reference prices, hours/location, and FAQs.

1 endpoint6 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://dentaldigitalcenter.com/mcp

No auth detected

MCP server metadata

Name: dental-digital-center
Version: 1.1.0

Capabilities

tools

Server instructions

Public read-only information server of Dental Digital Center, a dental clinic in Buenos Aires, Argentina (Av. Corrientes 1189, piso 4). Use it to answer questions about the clinic's treatments, reference prices ("desde", in Argentine pesos), opening hours, location and how to book. Content is in Spanish. Prices are reference values subject to in-person clinical evaluation: never present them as a quote, a diagnosis or medical advice. The server cannot book appointments; direct the user to WhatsApp, phone or the contact page (see how_to_book).

Known tools 6

get_clinic_info

Address, opening hours, phone/WhatsApp, how to get there, technology used and the professional team of Dental Digital Center (dental clinic in Buenos Aires, Argentina).

Inferred read-only

list_treatments

Lists every dental treatment offered (implants, smile design, veneers, prosthetics, endodontics, whitening, etc.

Inferred read-only

get_treatment

Details of one treatment: what it is, "from" reference price in ARS, installment options and a link.

Inferred read-only

get_prices

Full list of "from" reference prices in Argentine pesos (ARS) with installment options and the mandatory disclaimer (values are references subject to clinical evaluation, not a quote).

Inferred read-only

get_faq

Frequently asked questions about digital dentistry at the clinic (intraoral scanner, 3D printing, payment, diagnosis).

Potential side effects

how_to_book

How a patient can request an appointment: WhatsApp link, phone and contact page.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dental-digital-center]
url = "https://dentaldigitalcenter.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dental-digital-center": {
      "type": "http",
      "url": "https://dentaldigitalcenter.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dental-digital-center
Remote MCP URL: https://dentaldigitalcenter.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dental-digital-center": {
      "url": "https://dentaldigitalcenter.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dental-digital-center": {
      "type": "http",
      "url": "https://dentaldigitalcenter.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dental-digital-center",
  "transport": "streamable-http",
  "url": "https://dentaldigitalcenter.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.