listing MCP server
com.beycome/listingbeycome.comstreamable-httpv1.0.0Scanned
List on MLS, sell, show, compare and close your real estate property on beycome.
14 tools: 2 do something that can't be undone, 11 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 14
- Can send data out · 5
- 3 findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- 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 listing MCP server can do
The listing MCP server is published by beycome.com, a domain the MCP Registry verified. It has 14 tools. It can do things that cannot be undone, such as sending, paying or publishing (beycome_messages and beycome_reply_message) and create or change data (11 tools: beycome_signup, beycome_signin_start, beycome_signin_verify, beycome_check_coverage and 7 more), but cannot delete data. 1 tool only reads.
14 tools bring in text other people can write (beycome_signup, beycome_signin_start, beycome_signin_verify and 11 more); 5 tools can send data out of your system (beycome_signup, beycome_offers, beycome_showings and 2 more).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 10, 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.
14 tools
Can't be undone 2Claude Code: ask
beycome_messagesPost-publish stage — read the owner's buyer/inquiry messages (GET /messages).Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "post" and "message": it sends a message, which cannot be taken back.
- 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.
- outboundThe description's first verb is "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "beycome_messages" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "post" and "message": it sends a message, which cannot be taken back.
Description, as the server wrote it Post-publish stage — read the owner's buyer/inquiry messages (GET /messages). Read-only. Requires ``access_token``. Two modes: - Omit ``thread`` → lists the ~20 most recent conversations, newest first, one row per thread (the latest message in each). Useful fields per row: ``address``, ``prop_id``, ``prop_status``, ``msg`` (latest text), ``subject``, ``requested_by`` / ``email`` (the other party), ``thread``, ``read_msg`` ("0" = unread), ``attachments``, and ``message_type`` (``sender`` if the owner wrote the latest message, else ``receiver``). - Pass ``thread`` → returns that one conversation in full, oldest-first. Use the ``thread`` value from a list row to drill in. The list is not paginated here on purpose (the upstream ``page`` param is overloaded — it sets both page size and page number — so it is not exposed). Soft-deleted messages are dropped after paging, so a page may hold fewer than 20 rows; that is not an error. The payload is a bare array under ``data``. A 401 means the token is no longer valid (logged out, or very old) — re-authenticate with `beycome_signin_start` then `beycome_signin_verify`. To answer a message, use `beycome_reply_message`.
Annotations the server declares
- title: Read buyer/inquiry messages
- readOnlyHint: true
- openWorldHint: true
beycome_reply_messagePost-publish stage — reply to a buyer/inquiry message (POST /messages/reply).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "beycome_reply_message" says "reply": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "beycome_reply_message" says "reply": it sends or publishes something to other people.
Description, as the server wrote it Post-publish stage — reply to a buyer/inquiry message (POST /messages/reply). Sends a real message and queues a real email notification to the recipient, so the text you send is final — treat this as a live send, not a draft. ALWAYS improve the user's drafted reply before sending: fix grammar, spelling, punctuation, capitalization, and formatting, and tighten wording for a clear, professional tone — while preserving their meaning and intent. Send the corrected version, never the raw draft. When the user says "reply saying X", treat X as a rough draft to polish, not literal text to send verbatim. Requires ``to_user_id`` (the counterparty), ``message``, and ``access_token``. For a threaded reply pass the original ``thread`` verbatim and omit ``subject`` (the server prefixes "Re: <original subject>"). To find ``to_user_id``, open the conversation with `beycome_messages` and take the participant id that is not the signed-in owner. Success is 201 with ``data.id`` set to the new message id. Failures come back as 400 with a plain message: "User not found." (bad ``to_user_id``), "You cannot send a message to yourself." (``to_user_id`` is the sender), or "Invalid parameters" (e.g. empty/over-long ``message``). A 401 means the token is no longer valid — re-authenticate with `beycome_signin_start` then `beycome_signin_verify`.
Annotations the server declares
- title: Reply to a buyer/inquiry message
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Changes things 11Claude Code: ask
beycome_check_coverageDiscovery stage — is this state served by beycome MLS?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 Discovery stage — is this state served by beycome MLS? (GET /mls/is-covered). No account or prop_id needed. Use before listing to confirm beycome operates in the property's state; ``is_active: true`` means covered. If not covered, the listing flow does not apply.
Annotations the server declares
- title: Check beycome MLS coverage
- readOnlyHint: true
- openWorldHint: true
beycome_compsDiscovery stage — sold comparable listings near a location (GET /comps).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 Discovery stage — sold comparable listings near a location (GET /comps). No account or prop_id needed. Supports price / beds / baths / area / lot / type filters. Use during discovery to support pricing alongside `beycome_estimate`. Slow endpoint: a cold query can take up to ~1 minute to respond — this is normal, you can always retry the call if it times out. Photo URL and listing-link fields are stripped from the records to keep the response small.
Annotations the server declares
- title: Find sold comparable listings
- readOnlyHint: true
- openWorldHint: true
beycome_estimateDiscovery stage — estimate a property's SALE value (beycome CMA + Zillow Zestimate).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 Discovery stage — estimate a property's SALE value (beycome CMA + Zillow Zestimate). No account or prop_id needed. Returns both estimates plus suggested pricing strategies (fast / balanced / max). Use during discovery to set a list price; pair with `beycome_comps`. For rental inquiries, use `beycome_rental_estimate` instead.
Annotations the server declares
- title: Estimate property sale value
- readOnlyHint: true
- openWorldHint: true
beycome_offersPost-publish stage — offers received on the owner's listings (GET /offers).Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "post": a word for a change.
- 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.
- outboundThe description's first verb is "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "beycome_offers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "post": a word for a change.
Description, as the server wrote it Post-publish stage — offers received on the owner's listings (GET /offers). Used once a listing is live. Requires ``access_token``. Returns a paginated list (20 per page; pass ``page`` to advance) of every offer across all of the signed-in user's listings — each entry is the full offer record (buyer, price, contingencies, dates, status). Read-only. There is no server-side ``prop_id`` filter; to show offers for one listing, filter client-side on each offer's ``prop_id``. Responding to an offer (accept / reject / counter) is not exposed here.
Annotations the server declares
- title: View offers received
- readOnlyHint: true
- openWorldHint: true
beycome_questionnaire_linkQuestionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link).Reads text others writeNo findings
Why it is in this group
- The name "beycome_questionnaire_link" says "link": a word for a change.
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 Questionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link). Requires a PAID listing (premium active, Flat/Yes) — whether the user just paid on the submit-property page (`beycome_submit_property_link`) or already had a paid listing with the questionnaire still pending. Returns a pre-authorized link (expires in 7 days) — this tool only hands back the URL; everything else happens in the browser, with no login step. Present the URL and tell the user that on the page they will: 1. review the pre-filled MLS questionnaire and complete any fields Beycome couldn't pre-fill, 2. upload property photos and the required documents, 3. review and submit. After they submit, the listing goes live within about 48 hours, provided all the paperwork clears. Failure modes to relay plainly: 403 — the token is not the owner's; 422 — the listing is not paid yet, or the questionnaire was already submitted; 401 — bad/missing token.
Annotations the server declares
- title: Get MLS questionnaire link
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
beycome_rental_estimateDiscovery stage — estimate a property's monthly RENT (POST /gemini-estimate).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 Discovery stage — estimate a property's monthly RENT (POST /gemini-estimate). No account or prop_id needed. Pairs with `beycome_estimate`, but this tool is SPECIFICALLY for rental estimates: use it ONLY for rental inquiries or for properties that have a unit number. For sale-price estimates, use `beycome_estimate`. Returns ``rentEstimate`` (e.g. "$2,600"), ``rentEstimateRange`` (e.g. "$2,400 - $2,800"), and the ``sources`` the figure was grounded on (source URLs are stripped to keep the response small). Caveat: an unrecognized address still returns ``success: true`` with a generic market-average rent — check that the source titles actually reference the property's address/city before trusting the number; if they don't, treat the result as unavailable and ask the user to verify the address.
Annotations the server declares
- title: Estimate monthly rent
- readOnlyHint: true
- openWorldHint: true
beycome_showingsPost-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events).Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "post": a word for a change.
- 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.
- outboundThe description's first verb is "post": it sends or publishes something to other people.
Findings
- Warn
The server marks "beycome_showings" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "post": a word for a change.
Description, as the server wrote it Post-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events). Used once a listing is live. The API requires the date range, so it defaults to today → +90 days when omitted (``from_date`` / ``to_date`` are ``YYYY-MM-DD``, with ``to_date`` on or after ``from_date``). ``prop_id`` filters to one listing; omit it for every listing the user owns. The response always mixes ALL event kinds — each event carries a ``type`` field (``showing`` / ``open_house`` / ``offer``). There is no server-side type filter; when the user asks for one kind, filter on that field yourself.
Annotations the server declares
- title: View showings calendar
- readOnlyHint: true
- openWorldHint: true
beycome_signin_startAccount stage — send a one-time sign-in code (POST /auth/check-email).Reads text others writeNo findings
Why it is in this group
- The name "beycome_signin_start" says "start": a word for a change.
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 Account stage — send a one-time sign-in code (POST /auth/check-email). beycome is passwordless — never ask the user for a password. This emails the user a 6-digit code (a second, different code also goes out by SMS; either one works). Ask the user for the code they received, then exchange it for the access_token with `beycome_signin_verify`. Read the response body, not the HTTP status — the envelope's ``ok`` mirrors the HTTP status, and auth failures here still return 2xx. Always check ``data.success``: - ``success: true`` (201, "Email sent") — code sent; ask the user for it. - ``success: false`` with "Email not found." (HTTP 200, ``ok: true``) — no account for this email; run `beycome_signup` instead (signup also sends a code). - HTTP 422 (``ok: false``) — the email matched a secondary address; the body still matters: it hints the masked primary login email to use instead. Codes stay valid for 30 minutes. Re-running this tool sends a fresh code and invalidates the old one. Rate-limited (5/min and 100/day per email) — never call it in a loop or as an automatic retry.
Annotations the server declares
- title: Send one-time sign-in code
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
beycome_signin_verifyAccount stage — exchange the one-time code for the access_token (POST /auth/validate-code).Reads text others writeNo findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
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 Account stage — exchange the one-time code for the access_token (POST /auth/validate-code). The gateway to the listing flow. Call after `beycome_signin_start` or `beycome_signup` (both send the code) with the 6-digit code the user received. On success the Bearer token is at ``data.data.access_token`` (``expires_in`` gives its lifetime in seconds — tokens are long-lived, so mid-session expiry is rare). Pass it as ``access_token`` to every authenticated tool: `beycome_submit_property_link`, `beycome_get_my_listings`, `beycome_questionnaire_link`, `beycome_offers`, `beycome_showings`, `beycome_messages`, and `beycome_reply_message`. IMPORTANT — persist the token: save the access_token to your long-term memory/context (and tell the user you have done so). Save it together with the account ``email``, which disambiguates multi-account users and lets you match the right token to the right person. In future sessions, scheduled tasks, and crons, reuse the saved token instead of asking the user to sign in again — that is what makes autonomous workflows (e.g. "check my messages every morning") possible. Before signing a user in, check your memory for an existing token for that email and try it first; only restart the sign-in flow on a 401. The next step depends on where the user is: - No listing yet → `beycome_submit_property_link` to create one. - Has a listing already (or unsure) → `beycome_get_my_listings` to find it; if it is paid but the MLS questionnaire is not submitted, follow with `beycome_questionnaire_link`. - Listing already live → skip straight to the post-publish tools (`beycome_messages`, `beycome_showings`, `beycome_offers`). A wrong or expired code returns HTTP 200 with ``success: false`` and "Invalid code." — check ``data.success``, not the envelope's ``ok``. Codes expire after 30 minutes; if expired, request a fresh one with `beycome_signin_start` (don't retry blindly — sends are rate-limited).
Annotations the server declares
- title: Verify sign-in code
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
beycome_signupAccount stage — register a new beycome user (POST /auth/register).Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Account stage — register a new beycome user (POST /auth/register). Use when the owner has no account yet. beycome is passwordless: registering automatically emails the user a 6-digit sign-in code, so the next step is `beycome_signin_verify` with that code — do NOT call `beycome_signin_start` after signup, the code is already on its way. If the email is already registered, this still just sends a sign-in code (signup doubles as signin-start). Requires ``firstname`` and ``phone``; validation errors come back as HTTP 400 with an ``errors`` array. No prop_id needed.
Annotations the server declares
- title: Sign up for beycome
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
beycome_submit_property_linkListing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link).Reads text others writeNo findings
Why it is in this group
- The name "beycome_submit_property_link" says "submit": a word for a change.
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 Listing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link). Call AFTER signing in (`beycome_signin_verify`). User-scoped — no prop_id exists yet. Returns a pre-authorized link (expires in 7 days) — this tool only hands back the URL; the listing is created in the browser, with no login step. Present the URL and tell the user that on the page they will: 1. fill out their property's information, 2. set a price, 3. choose a package and any add-ons, 4. pay. Tell them to return to the chat once payment is complete. Prefill: the page accepts prefill params baked into the signed URL. - list_address: the full property address. By this stage the user has already told Claude their address (discovery ran on it), so ALWAYS pass list_address so the page opens pre-filled. - package: the page PRESET INDEX (1-4), not a payment reference — 1 = Basic $99 2 = Enhanced $399 3 = Concierge $999 4 = Basic + Title $199 WARNING: this is the page preset index, NOT an internal payPremiumOpt reference number. Passing a payPremiumOpt reference here is wrong. Only pass package if the user has clearly chosen a tier in chat; otherwise omit it and let them pick on the page. Failure modes to relay plainly: 401 — bad/unverified token. This page is THE way to create a listing — the property is created, priced, and paid for there; there is no in-chat alternative. After the user returns, call `beycome_get_my_listings` to recover the new prop_id, then `beycome_questionnaire_link`.
Annotations the server declares
- title: Get create-listing link
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
beycome_get_my_listingsRecovery stage — the signed-in user's properties (GET /properties).Reads text others writeNo findings
Why it is in this group
- The name "beycome_get_my_listings" says "get": a word for reading.
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 Recovery stage — the signed-in user's properties (GET /properties). Token-scoped RESO list endpoint on the normal api base. Two main uses: - After the user finishes the submit-property page (`beycome_submit_property_link`): find the newly created listing (typically the newest entry), CONFIRM the address with the user, then use its id as ``prop_id`` for `beycome_questionnaire_link`. - As the entry point for a returning user who already has listings (or references "my listing" without an id): locate the listing and read its status to pick the next step — paid but questionnaire pending → `beycome_questionnaire_link`; already live → the post-publish tools (`beycome_messages`, `beycome_showings`, `beycome_offers`).
Annotations the server declares
- title: Get my listings
- readOnlyHint: true
- openWorldHint: true
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write14
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- 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:34 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://mcp.beycome.com/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata
- https://mcp.beycome.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.beycome.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 13 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://mcp.beycome.com/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://mcp.beycome.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.beycome.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
- Warnbeycome_offers
The server marks "beycome_offers" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "post": a word for a change.
- Warnbeycome_showings
The server marks "beycome_showings" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "post": a word for a change.
- Warnbeycome_messages
The server marks "beycome_messages" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "post" and "message": it sends a message, which cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 13 -> 0 (and 7 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 13 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://mcp.beycome.com/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://mcp.beycome.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.beycome.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http listing https://mcp.beycome.com/mcpclaude mcp add --transport http listing https://mcp.beycome.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__listing__beycome_get_my_listings"
],
"ask": [
"mcp__listing__beycome_signup",
"mcp__listing__beycome_signin_start",
"mcp__listing__beycome_signin_verify",
"mcp__listing__beycome_check_coverage",
"mcp__listing__beycome_estimate",
"mcp__listing__beycome_rental_estimate",
"mcp__listing__beycome_comps",
"mcp__listing__beycome_questionnaire_link",
"mcp__listing__beycome_submit_property_link",
"mcp__listing__beycome_offers",
"mcp__listing__beycome_showings",
"mcp__listing__beycome_messages",
"mcp__listing__beycome_reply_message"
],
"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 listing. Review it before you use it.
Capability tags behind 14 rules
- mcp__listing__beycome_signup untrusted-input, outbound
- mcp__listing__beycome_signin_start untrusted-input
- mcp__listing__beycome_signin_verify untrusted-input
- mcp__listing__beycome_check_coverage untrusted-input
- mcp__listing__beycome_estimate untrusted-input
- mcp__listing__beycome_rental_estimate untrusted-input
- mcp__listing__beycome_comps untrusted-input
- mcp__listing__beycome_questionnaire_link untrusted-input
- mcp__listing__beycome_submit_property_link untrusted-input
- mcp__listing__beycome_get_my_listings untrusted-input
- mcp__listing__beycome_offers untrusted-input, outbound
- mcp__listing__beycome_showings untrusted-input, outbound
- mcp__listing__beycome_messages untrusted-input, outbound
- mcp__listing__beycome_reply_message untrusted-input, outbound
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.beycome/listing/verify?hash=655f2ebbd1576c7d512908816438d9c99e9e15ada7cf6f92de4b9884f1676005" | jq -e '.changed == false'Pinned hash 655f2ebbd157, from Nov 10, 2026, 12:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.beycome/listing/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.beycome/listing)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:51 UTC.
listing MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the listing MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 13 of which can change, send or delete something, and 3 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 listing MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the listing MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: beycome_messages and beycome_reply_message.
What tools does the listing MCP server have?
- 14 tools: 2 irreversible, 11 write, 1 read. beycome_messages, beycome_reply_message, beycome_signup, beycome_signin_start, beycome_signin_verify, beycome_check_coverage, beycome_estimate, beycome_rental_estimate and 6 more.
Does the listing MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the listing MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): beycome_signup, beycome_offers, beycome_showings, beycome_messages and beycome_reply_message.
Has the listing MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.