Dental Digital Center (Buenos Aires)
REMOTE · DENTALDIGITALCENTER.COM
Read-only info for a Buenos Aires dental clinic: treatments, reference prices, hours and booking.
Available components
Last scanned (11 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 462 tokens (~77/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://dentaldigitalcenter.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.dentaldigitalcenter.com | CN=YR2,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 68262108fdc6fe8235e82bba66f6a526230 |
| SANs: *.dentaldigitalcenter.com, dentaldigitalcenter.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dentaldigitalcenter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dentaldigitalcenter.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dentaldigitalcenter.com/mcp | Verified | 200 | |
| http (plaintext) | http://dentaldigitalcenter.com/mcp | Inconclusive | 405 |
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 →
get_clinic_info Clinic information ~49
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). Content in Spanish.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_faq Frequently asked questions ~63
Frequently asked questions about digital dentistry at the clinic (intraoral scanner, 3D printing, payment, diagnosis). Optional topic filter.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional keyword to filter questions (Spanish), e.g. "escáner", "precios". |
No output schema declared.
No examples provided.
get_prices Reference price list ~51
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). Includes the date the prices were last updated.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_treatment Treatment details ~99
Details of one treatment: what it is, "from" reference price in ARS, installment options and a link. Accepts a treatment key or free text such as "implante", "carillas", "blanqueamiento", "limpieza" or "endodoncia". Content in Spanish.
| Name | Type | Req | Description |
|---|---|---|---|
| treatment | string | yes | Treatment name, key or keyword (Spanish), e.g. "implante de titanio", "carillas". |
No output schema declared.
No examples provided.
how_to_book How to book an appointment ~33
How a patient can request an appointment: WhatsApp link, phone and contact page. This server cannot create bookings itself.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_treatments List treatments ~51
Lists every dental treatment offered (implants, smile design, veneers, prosthetics, endodontics, whitening, etc.) with a one-line summary and its "from" reference price in ARS.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Dental Digital Center (Buenos Aires) MCP server?
Dental Digital Center (Buenos Aires) is a hosted endpoint at https://dentaldigitalcenter.com/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 · dentaldigitalcenter.com
claude mcp add --transport http com-dentaldigitalcenter-mcp 'https://dentaldigitalcenter.com/mcp'
What is the Dental Digital Center (Buenos Aires) MCP server?
Dental Digital Center (Buenos Aires) is an MCP server listed in the public MCP registry as com.dentaldigitalcenter/mcp. Read-only info for a Buenos Aires dental clinic: treatments, reference prices, hours and booking. This page covers its hosted endpoint (https://dentaldigitalcenter.com/mcp).
Is the Dental Digital Center (Buenos Aires) MCP server safe to use?
Dental Digital Center (Buenos Aires) scores 74 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 Dental Digital Center (Buenos Aires) MCP server expose?
Dental Digital Center (Buenos Aires) exposes 6 tools: get_clinic_info, list_treatments, get_treatment, get_prices, get_faq, how_to_book. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.
Does the Dental Digital Center (Buenos Aires) MCP server require authentication?
No. We connected to Dental Digital Center (Buenos Aires) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dental Digital Center (Buenos Aires) MCP server still maintained?
Dental Digital Center (Buenos Aires) 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.