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

nextcore-stays

https://homestaynextcore.org

Registry code: 04f3efc7351238b8

api record

NextCore (homestaynextcore.org) lists homestays, villas and hotels in Da Lat (Lam Dong, Vietnam); call list_locations for current destinations. Read-only: search stays, read details, check availability and get a price quote for exact dates. To book, give the human the booking_url — this server cannot create bookings or take payment. Dates are YYYY-MM-DD in Vietnam time (UTC+7); prices are VND and include service fees.

endpoint
https://homestaynextcore.org/api/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 nextcore-stays live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is nextcore-stays free to use?
Yes — the hub reached it with no key and no payment.
What tools does nextcore-stays have?
4 tools: get_stay, check_availability, search_stays, list_locations.
Is nextcore-stays 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
3,344ms

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.

  • search_stays open 1h ago

    Search bookable stays by location, dates and guests. With dates, returns only stays with a room free for every night, the lowest nightly price and stay total (VND, fees included), plus booking_url for the human.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1
        },
        "guests": {
          "type": "integer",
          "default": 2,
          "maximum": 50,
          "minimum": 1,
          "description": "Number of guests."
        },
        "check_in": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Check-in date. Give together with check_out to get only stays free for the whole stay."
        },
        "location": {
          "type": "string",
          "maxLength": 200,
          "description": "Location slug from list_locations. Omit to search everywhere."
        },
        "check_out": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Check-out date (max 30 nights after check_in)."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • list_locations open 1h ago

    List destinations that currently have bookable stays, with the number of stays each.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_stay unknown 1h ago

    Get one stay: description, house rules, check-in/out times, amenities, rooms (capacity, bedrooms), images and booking_url.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 200,
          "description": "Stay slug from search_stays (e.g. \"lyns-hotel\")."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • check_availability unknown 27h ago

    Day-by-day availability for a month, and — when check_in/check_out are given — a quote: every room free for the whole stay with price per night, total (VND) and a room-specific booking_url. If nothing is free, suggested_dates gives the nearest free stay of the same length.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 200,
          "description": "Stay slug from search_stays (e.g. \"lyns-hotel\")."
        },
        "month": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}$",
          "description": "Calendar month YYYY-MM (current month up to 12 months ahead). Defaults to the check_in month or this month."
        },
        "guests": {
          "type": "integer",
          "default": 2,
          "maximum": 50,
          "minimum": 1,
          "description": "Number of guests."
        },
        "check_in": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "With check_out: returns a quote with per-room price and total."
        },
        "check_out": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        }
      },
      "additionalProperties": false
    }
    arguments 35 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 04f3efc7351238b8.

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