SelectBNBs Verify MCP server
com.selectbnbs/verifyselectbnbs.comstreamable-httpv1.0.0Scanned
Check whether a short-term rental in South Korea is registered, using official government records.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SelectBNBs Verify MCP server can do
The SelectBNBs Verify MCP server is published by selectbnbs.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: verify_listing_registration), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (verify_listing_registration).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
verify_listing_registrationCheck whether a short-term rental listing (Airbnb, guesthouse, hanok stay, homestay, pension) is licensed and registered with the government, using official government registry rec…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a stay's government registration (South Korea)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
get_permit_recordFetch one accommodation permit record from official South Korean government data, by its government management number (e.g.No findings
Why it is in this group
- The name "get_permit_record" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one government permit record (South Korea)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://selectbnbs.com/mcp: tools/list returned 2 tools to an anonymous client, including verify_listing_registration (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http verify https://selectbnbs.com/mcpclaude mcp add --transport http verify https://selectbnbs.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__verify__get_permit_record"
],
"ask": [
"mcp__verify__verify_listing_registration"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as verify. Review it before you use it.
Capability tags behind 1 rule
- mcp__verify__verify_listing_registration untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.selectbnbs/verify/verify?hash=96c5ac0399491fccb3330aede39895037819b43d5fe342c26c6e5890497666c1" | jq -e '.changed == false'Pinned hash 96c5ac039949, from Nov 14, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.selectbnbs/verify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.selectbnbs/verify)Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.
SelectBNBs Verify MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SelectBNBs Verify MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SelectBNBs Verify MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SelectBNBs Verify MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SelectBNBs Verify MCP server have?
- 2 tools: 1 write, 1 read. verify_listing_registration and get_permit_record.
Does the SelectBNBs Verify MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SelectBNBs Verify MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SelectBNBs Verify MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.