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

helprent-danang

https://helprentdanang.com

Registry code: 35bd5fa3e46d82fe

api record

Read-only search over long-term rentals in Da Nang, Vietnam. Free daily allowance; past it the endpoint answers HTTP 402 with an x402 challenge (USDC on Base, Solana, Arc or Stellar).

endpoint
https://helprentdanang.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
10 · newcomer
_ is it live, free and safe measured by this hub
Is helprent-danang live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is helprent-danang free to use?
Yes — the hub reached it with no key and no payment.
What tools does helprent-danang have?
6 tools: get_listing, fetch, find_buildings, market_stats, search, search_listings.
Is helprent-danang 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
404ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 644 checks · signed record
  • down → live
_ what it is for
topic
real estate & construction property & real estate
used for
  • search long-term rentals in da nang
  • get rental listing details
  • get median rents by district
  • find managed apartment buildings
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 2 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
2

last 2026-10-23

received on chain
0.02 USDC

counted from three payers (thin, concentrated)

_ what it can do 6 tools
4 open 2 never probed 4 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.

  • find_buildings reads open 6h ago

    Apartment buildings with a manager, by district.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "string"
    },
    "district": {
      "type": "string"
    },
    "page_size": {
      "type": "string"
    }
  }
}
    arguments 14 lines
  • market_stats reads open 6h ago

    Median rents by size and district, the middle half of asking prices with the sample behind each figure, and how many listings are on the board. Recomputed nightly.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • search reads open 3h ago

    Search long-term rentals in Da Nang from a plain phrase such as '2 bedroom apartment in Son Tra under 15 million'. Returns up to 10 results with id, title and url; pass an id to fetch for the full listing. Contact details are never included, send the person to the url.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • search_listings reads open 6h ago

    Search long-term rental listings in Da Nang by city, district, type, bedrooms and price. Returns listing URLs; contact details are not included, send the person to the URL.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string"
    },
    "page": {
      "type": "string"
    },
    "type": {
      "type": "string"
    },
    "bedrooms": {
      "type": "string"
    },
    "district": {
      "type": "string"
    },
    "page_size": {
      "type": "string"
    },
    "price_max": {
      "type": "string"
    },
    "price_min": {
      "type": "string"
    }
  }
}
    arguments 29 lines
  • get_listing reads unknown 3h ago

    One listing in full, including its description.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • fetch reads unknown 3h ago

    The full text of one listing by the id that search returned.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}
    arguments 11 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 35bd5fa3e46d82fe.

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