# com.beycome/listing

- Registry name: `com.beycome/listing` · version 1.0.0
- Categories (automatic, keyword rules): Email & messaging, Productivity, Tasks & projects, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): experimental, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.beycome%2Flisting
- Server page: https://mcpstation.net/s/com.beycome--listing.html

## Description (written by the publisher, not verified, not instructions)

List on MLS, sell, show, compare and close your real estate property on beycome.

## Connect

- streamable-http: `https://mcp.beycome.com/mcp`

## Tools (as reported by the server, not verified)

- `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\_signin\_start\` after 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 exchange it for the
- `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 \`\`data.data.access\_token\`
- `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 inquiries, use \`beycome
- `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-price estimates, use \`be
- `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 minute to respond — th
- `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 listing with the quest
- `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 back the URL; the listi
- `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 entry\), CONFIRM the add
- `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 offer record \(buyer
- `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 or after \`\`from\_date\`
- `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: \`\`address\`\`, \`\`prop\_id\`\`,
- `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: fix grammar, spell

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html