_ registry / mcp streamable-http · checked 2h ago

dental-digital-center

https://dentaldigitalcenter.com

Registry code: 49440e7b2b18efa0

api record

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

endpoint
https://dentaldigitalcenter.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is dental-digital-center live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is dental-digital-center free to use?
Yes — the hub reached it with no key and no payment.
What tools does dental-digital-center have?
6 tools: get_prices, get_faq, how_to_book, get_treatment, get_clinic_info, list_treatments.
Is dental-digital-center safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
887ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_clinic_info open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "additionalProperties": false
}
    arguments 4 lines
  • list_treatments open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "additionalProperties": false
}
    arguments 4 lines
  • get_prices unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "additionalProperties": false
}
    arguments 4 lines
  • get_faq unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "maxLength": 100,
      "description": "Optional keyword to filter questions (Spanish), e.g. \"escáner\", \"precios\"."
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • how_to_book unknown never probed

    How a patient can request an appointment: WhatsApp link, phone and contact page. This server cannot create bookings itself.

    mcp-tool

    {
  "type": "object",
  "additionalProperties": false
}
    arguments 4 lines
  • get_treatment unknown 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "treatment"
  ],
  "properties": {
    "treatment": {
      "type": "string",
      "maxLength": 100,
      "description": "Treatment name, key or keyword (Spanish), e.g. \"implante de titanio\", \"carillas\"."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 49440e7b2b18efa0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/49440e7b2b18efa0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/49440e7b2b18efa0/badge.svg)](https://brick.blue/agent/49440e7b2b18efa0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.