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

SelectBNBs Verify

https://selectbnbs.com

Registry code: 3b5974aa64371c10

api record

SelectBNBs Verify checks whether a short-term rental (Airbnb, guesthouse, hanok stay, homestay) is licensed with the government, using official government registry records that are hard to access directly. SelectBNBs Verify covers South Korea today; more countries are coming. Use verify_listing_registration with the listing's whole Registration details box (Region of issuance, Licence type, Licence number); ask the traveler to copy it if you do not have it. A registered name or Korean road address is a weaker fallback. Use get_permit_record only when you already have a government management…

endpoint
https://selectbnbs.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
0 · newcomer
_ is it live, free and safe measured by this hub
Is SelectBNBs Verify live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is SelectBNBs Verify free to use?
Yes — the hub reached it with no key and no payment.
What tools does SelectBNBs Verify have?
2 tools: get_permit_record, verify_listing_registration.
Is SelectBNBs Verify 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
98.7%

90 days 98.9%· all time 98.9%

latency
557ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 276 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • verify a short-term rental is licensed
  • fetch an accommodation permit record
takes → gives
text → data
tools
2 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: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ 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.

  • get_permit_record reads unknown 4h ago

    Fetch one accommodation permit record from official South Korean government data, by its government management number (e.g. AGCV065100002024000451), optionally with its Korean issuing region, or by registered business name together with the Korean issuing region (e.g. name 'Jobs', region '서울특별시 종로구'). SelectBNBs Verify covers South Korea today; more countries are coming. It takes one of these identifiers and does not read text copied from a listing. Returns one record (status, category, permit date, record page link, citation) or says why no single record could be chosen. Never lists or browses records.

    mcp-tool

    {
      "type": "object",
      "title": "get_permit_recordArguments",
      "required": [
        "country"
      ],
      "properties": {
        "name": {
          "type": "string",
          "title": "Name",
          "default": "",
          "maxLength": 200,
          "description": "Registered business name (사업장명). Send together with region."
        },
        "region": {
          "type": "string",
          "title": "Region",
          "default": "",
          "maxLength": 200,
          "description": "Korean issuing region in Korean, e.g. 서울특별시 종로구. Required with name; optional with management_number, where it picks the local government that issued a shared number."
        },
        "country": {
          "type": "string",
          "title": "Country",
          "maxLength": 40,
          "minLength": 1,
          "description": "ISO 3166-1 alpha-2 code of the country where the stay is, e.g. KR. Only KR (South Korea) is covered today; other countries return 'not covered yet'."
        },
        "management_number": {
          "type": "string",
          "title": "Management Number",
          "default": "",
          "maxLength": 60,
          "description": "Full government management number, e.g. AGCV065100002024000451. Urban-homestay and hanok numbers (CDFI...) repeat across local governments; send those with region."
        }
      }
    }
    arguments 37 lines
  • verify_listing_registration reads unknown 4h ago

    Check whether a short-term rental listing (Airbnb, guesthouse, hanok stay, homestay, pension) is licensed and registered with the government, using official government registry records that are hard to access directly. SelectBNBs Verify covers South Korea today; more countries are coming. Use it when someone asks whether a Korean Airbnb or guesthouse is legal, licensed, registered or real. Pass the listing's 'Registration details' box exactly as shown (Region of issuance, Licence type, Licence number). If the traveler has not copied it yet, ask them to; a registered name or Korean road address is a weaker fallback. Returns the official permit status and its as-of date, the registered business name, permit category and address, a link to the public record page, and what the traveler should compare with their listing. One listing per call; no bulk search.

    mcp-tool

    {
      "type": "object",
      "title": "verify_listing_registrationArguments",
      "required": [
        "listing_details",
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "title": "Country",
          "maxLength": 40,
          "minLength": 1,
          "description": "ISO 3166-1 alpha-2 code of the country where the stay is, e.g. KR. Only KR (South Korea) is covered today; other countries return 'not covered yet'."
        },
        "language": {
          "enum": [
            "en",
            "ja",
            "zh-Hant"
          ],
          "type": "string",
          "title": "Language",
          "default": "en",
          "description": "Language for explanations and next steps: en (default), ja or zh-Hant."
        },
        "listing_details": {
          "type": "string",
          "title": "Listing Details",
          "maxLength": 4000,
          "minLength": 1,
          "description": "Text copied from ONE listing, as shown: ideally the whole Registration details box (e.g. 'Region of issuance: 서울특별시 종로구 / Licence type: 외국인관광도시민박업 / Licence number: 2025-000006'). A registered name, Korean road address or government management number also works, less reliably."
        }
      }
    }
    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 3b5974aa64371c10.

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

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.