_ registry / mcp streamable-http · checked 49m ago

dhananjaya-villas

https://dhananjaya.id

Registry code: d6315e058c099386

api record

Dhananjaya Hospitality manages 40+ private villas and boutique resorts in Bali (Ubud, Sebatu, Tegallalang, Canggu, Pererenan and East Bali). Use search_villas for a stay, villa_details for one villa, check_availability for exact room prices, and current_offers for the website deals. Prices are live, in IDR, per stay, tax and service included, already less the website promotion the stay qualifies for. Always give the guest the booking_url: booking and payment happen on book.dhananjaya.id, the official Dhananjaya booking site.

endpoint
https://dhananjaya.id/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 dhananjaya-villas live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is dhananjaya-villas free to use?
Yes — the hub reached it with no key and no payment.
What tools does dhananjaya-villas have?
4 tools: villa_details, check_availability, search_villas, current_offers.
Is dhananjaya-villas 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
295ms

last good check

priced tools
0

of 4 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 4 tools
1 open 3 never probed 1 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.

  • current_offers open 49m ago

    The promotions running on book.dhananjaya.id (e.g. Best Rate Guarantee, Early Bird, Stay Longer) and their conditions.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • villa_details unknown never probed

    Description, location, facilities, house rules, Google rating, room types and photos of one villa.

    mcp-tool

    {
  "type": "object",
  "required": [
    "property_code"
  ],
  "properties": {
    "property_code": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • check_availability unknown 49m ago

    Every available room type and rate plan of one villa for the dates, with the price for the stay and a booking link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "property_code",
    "check_in",
    "check_out"
  ],
  "properties": {
    "adults": {
      "type": "integer",
      "default": 2,
      "maximum": 12,
      "minimum": 1
    },
    "check_in": {
      "type": "string"
    },
    "check_out": {
      "type": "string"
    },
    "property_code": {
      "type": "string",
      "description": "Villa code from search_villas, e.g. AKSH"
    }
  }
}
    arguments 26 lines
  • search_villas unknown 49m ago

    Find Dhananjaya villas and resorts in Bali that are available for the dates, with the lowest price for the stay and a booking link. Optionally filter by area (e.g. Ubud, Canggu, East Bali), maximum price per night, or breakfast included.

    mcp-tool

    {
  "type": "object",
  "required": [
    "check_in",
    "check_out"
  ],
  "properties": {
    "area": {
      "type": "string",
      "description": "Area or town, e.g. Ubud, Tegallalang, Sebatu, Canggu, Pererenan, East Bali"
    },
    "limit": {
      "type": "integer",
      "default": 8,
      "maximum": 20,
      "minimum": 1
    },
    "adults": {
      "type": "integer",
      "default": 2,
      "maximum": 12,
      "minimum": 1,
      "description": "Adults per room"
    },
    "check_in": {
      "type": "string",
      "description": "Arrival date, YYYY-MM-DD"
    },
    "breakfast": {
      "type": "boolean",
      "description": "Only rates with breakfast included"
    },
    "check_out": {
      "type": "string",
      "description": "Departure date, YYYY-MM-DD"
    },
    "max_price_per_night": {
      "type": "number",
      "description": "Maximum price per night in IDR"
    }
  }
}
    arguments 42 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 d6315e058c099386.

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