# Beycome Listing Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Beycome Listing

List your property on MLS, manage showings, offers and buyer messages

- Record: https://musedirectory.ai/connector/beycome-listing
- Category: Shopping & Commerce
- Developer: Beycome (https://www.beycome.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 844ms, checked 2026-09-28T07:31:03Z
- Endpoint: https://mcp.beycome.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T11:25:43Z)
- Source: Found in the official MCP Registry (com.beycome/listing) https://registry.modelcontextprotocol.io/v0/servers?search=com.beycome%2Flisting

Connect to Beycome to list residential properties on MLS, get price estimates and comparables, manage showings and open houses, review and respond to buyer offers and inquiries, and close sales. Passwordless sign-in via email code.

Example request: "Help me list my house for sale and show me what offers I've received"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Beycome Listing to help me. It is a free service with an MCP server at https://mcp.beycome.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- beycome_signup: 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_s
- beycome_signin_start: 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
- beycome_signin_verify: 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 ``dat
- beycome_check_coverage: 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.
- beycome_estimate: 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 inq
- beycome_rental_estimate: 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-pric
- beycome_comps: 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 mi
- beycome_questionnaire_link: 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 li
- beycome_submit_property_link: 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 bac
- beycome_get_my_listings: 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 ent
- beycome_offers: 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
- beycome_showings: 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 o
- beycome_messages: 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: ``addr
- beycome_reply_message: 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

Screening checks:
- MCP handshake: pass (Answered in 292ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.beycome.com, www.beycome.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (14 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)