_ registry / mcp + a2a HTTP+JSON · checked 2h ago

virohana-dental

https://virohanadentalclinic.com

Registry code: 4c80cc99fd854932

api record

Public information server for Virohana Dental Clinic in Rajajinagar, Bengaluru, India — a practice specialising in basal dental implants and same-day fixed teeth, led by Dr Roshini Shetty (MDS). All tools are READ-ONLY and return only public clinic information. Start with clinic_info(); use list_treatments() and get_treatment(<slug>) for procedures, location_and_hours() and contact_and_booking() for visiting, about_dentist() for the lead dentist, and oral_health_articles() for the blog. For appointments, list_consultation_windows() returns requestable 30-minute windows and…

endpoint
https://virohanadentalclinic.com/
door code
71b7ee35bf203c59
protocol
HTTP+JSON ·0.3
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 virohana-dental live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is virohana-dental free to use?
Yes — the hub reached it with no key and no payment.
What tools does virohana-dental have?
2 tools: clinic_info, book_consultation.
Is virohana-dental 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
99.2%

90 days 98.4%· all time 97.7%

latency
212ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 879 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get dental clinic information
  • list dental treatments
  • find clinic hours and location
  • request a dental consultation
  • read oral health articles
takes → gives
text → data, text
tools
1 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • clinic-info reads unknown never probed

    Look up public information about Virohana Dental Clinic: treatments offered and how each is performed, opening hours, address and directions, contact and booking routes, the lead dentist's background, oral-health articles, and answers to common questions. Served by the clinic's live MCP server. Call initialize, then tools/list, then the tool you need. Available tools: clinic_info, list_treatments, get_treatment(slug), location_and_hours, contact_and_booking, about_dentist, oral_health_articles, faqs, list_consultation_windows(days), request_consultation(window_start, patient_name, concern). Read-only: nothing here mutates clinic state or creates an appointment.

    clinicdentalinformationmcpread-onlyfree

  • book-consultation unknown never probed

    Hand a patient off to the clinic to book a consultation. Give the user the WhatsApp URL below: it opens a chat with the clinic on +91 74111 21611 with a booking request pre-filled, which the user sends themselves. This is a handoff, not an API. No appointment is created by fetching this URL, and an agent must never claim a booking has been made. Clinic staff confirm every appointment. To offer specific times first, call list_consultation_windows(days) on the MCP server at https://virohanadentalclinic.com/mcp for requestable 30-minute windows (Monday to Saturday, 09:00-20:00 Asia/Kolkata, default 7 days ahead, maximum 14), then request_consultation(window_start, patient_name, concern) to get the same WhatsApp handoff with the chosen window pre-filled. Windows are requestable, not confirmed — clinic staff confirm every appointment by WhatsApp or phone. Consultation fee is Rs 500, the only price the clinic publishes. Phone booking on +91 74111 21611 or +91 72049 02731 and the website contact form are equivalent alternatives. Bookable Monday to Saturday, 9:00 AM to 8:00 PM IST.

    bookingappointmentwhatsapphandoffhuman-confirmedfreemcp

_ try it over a2a 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 4c80cc99fd854932.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4c80cc99fd854932/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/4c80cc99fd854932/badge.svg)](https://brick.blue/agent/4c80cc99fd854932?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 knowoff the mcp door
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.