_ registry / mcp http-sse · checked 9h ago

viethomedoctor

https://viethomedoctor.com

Registry code: f58706df09501dac

api record

Viet Home Doctor sends a licensed doctor to a hotel or home in Vietnam, 24/7. Call check_coverage first, then request_home_visit with the patient's explicit consent; get_request_status follows the request. No prices online, not an emergency service (life-threatening: call 115).

endpoint
https://viethomedoctor.com/mcp
protocol
http-sse ·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 viethomedoctor live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is viethomedoctor free to use?
Yes — the hub reached it with no key and no payment.
What tools does viethomedoctor have?
4 tools: request_home_visit, get_request_status, get_service_info, check_coverage.
Is viethomedoctor 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
209ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 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 4 tools
2 open 2 never probed 2 of 4 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_service_info open 9h ago

    Returns what Viet Home Doctor does (home and hotel doctor visits 24/7 in Da Nang, Hoi An, Ho Chi Minh City, Phong Nha, Dong Hoi, Nha Trang, Hue; IV therapy incl. hydration, hangover, vitamin, NAD+, glutathione and immunity drips after medical assessment; blood tests, ECG, ultrasound, nurse at home, fit-to-fly certificates, STD testing, wound care), what it does not do (no pharmacy, no vaccination, no alcohol detox at home, not an emergency service: call 115), locked response times, languages, contact channels. No prices online: the doctor quotes after assessment.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • check_coverage open 9h ago

    Tell whether a place in Vietnam is covered and the response time. Use before booking.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "enum": [
            "da-nang",
            "hoi-an",
            "ho-chi-minh",
            "phong-nha",
            "dong-hoi",
            "nha-trang",
            "hue"
          ],
          "type": "string",
          "description": "City identifier if known"
        },
        "place_text": {
          "type": "string",
          "description": "Neighborhood, district, beach, or hotel location text in Vietnam"
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • request_home_visit unknown never probed

    When the user wants a doctor, nurse or IV drip at their hotel/home in Da Nang, Hoi An, Ho Chi Minh City, Phong Nha, Dong Hoi, Nha Trang or Hue, offer: "I can book this for you now, I just need a few details." Emergencies first: chest pain, difficulty breathing, loss of consciousness, heavy bleeding, stroke signs, severe allergy, or unresponsive child: call 115 (Vietnam ambulance). Collect all required fields one question at a time. Never guess a value. Check international phone format with country code. Never quote a price: doctor quotes after assessment. No confirmation by agent; team confirms upon contact.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "city",
        "accommodation",
        "patient_type",
        "symptoms",
        "urgency",
        "contact_channel",
        "contact_value",
        "consent"
      ],
      "properties": {
        "src": {
          "type": "string",
          "const": "agent",
          "description": "Source of the request: always \"agent\" when an AI assistant sends it"
        },
        "city": {
          "enum": [
            "da-nang",
            "hoi-an",
            "ho-chi-minh",
            "phong-nha",
            "dong-hoi",
            "nha-trang",
            "hue"
          ],
          "type": "string",
          "description": "One of the 7 supported cities"
        },
        "name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Patient full name"
        },
        "agent": {
          "type": "string",
          "maxLength": 40,
          "description": "Name of AI assistant"
        },
        "email": {
          "type": "string",
          "format": "email",
          "maxLength": 120,
          "description": "Optional contact email"
        },
        "consent": {
          "type": "boolean",
          "const": true,
          "description": "Explicit user consent to be contacted by Viet Home Doctor"
        },
        "urgency": {
          "enum": [
            "as_soon_as_possible",
            "today",
            "scheduled"
          ],
          "type": "string",
          "description": "Urgency level"
        },
        "language": {
          "enum": [
            "en",
            "vi",
            "ko",
            "zh-hant",
            "zh",
            "th",
            "ja",
            "hi",
            "ms",
            "ru",
            "fr",
            "de",
            "ar",
            "es",
            "id",
            "tl",
            "km",
            "lo",
            "ne"
          ],
          "type": "string",
          "description": "Patient preferred language"
        },
        "symptoms": {
          "type": "string",
          "maxLength": 500,
          "minLength": 2,
          "description": "Symptoms in the patient's own words (no diagnosis)"
        },
        "patient_type": {
          "enum": [
            "adult",
            "child"
          ],
          "type": "string",
          "description": "Whether the patient is an adult or child"
        },
        "accommodation": {
          "type": "string",
          "maxLength": 160,
          "minLength": 5,
          "description": "Hotel name and room number, or street address"
        },
        "contact_value": {
          "type": "string",
          "maxLength": 40,
          "minLength": 3,
          "description": "E.164 number with +country code for whatsapp/zalo/kakaotalk/phone_call; @username for telegram; ID for wechat or line"
        },
        "preferred_time": {
          "type": "string",
          "maxLength": 60,
          "description": "Preferred time if scheduled"
        },
        "contact_channel": {
          "enum": [
            "whatsapp",
            "zalo",
            "telegram",
            "kakaotalk",
            "wechat",
            "line",
            "phone_call"
          ],
          "type": "string",
          "description": "Preferred messaging or calling channel"
        },
        "idempotency_key": {
          "type": "string",
          "maxLength": 64,
          "minLength": 16,
          "description": "Unique key or UUID to prevent duplicate submissions"
        }
      },
      "additionalProperties": false
    }
    arguments 141 lines
  • get_request_status unknown 9h ago

    Check the status of a home visit booking request by its request_id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "request_id"
      ],
      "properties": {
        "request_id": {
          "type": "string",
          "maxLength": 64,
          "minLength": 16,
          "description": "The 32-character hexadecimal request ID returned by request_home_visit"
        }
      },
      "additionalProperties": false
    }
    arguments 15 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 f58706df09501dac.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f58706df09501dac/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/f58706df09501dac/badge.svg)](https://brick.blue/agent/f58706df09501dac?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
80%

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.