Skip to content
External endpointresponds

listing

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

Endpoint URL
https://mcp.beycome.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
179 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.beycome/listing

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
com.beycome/listing
Version
1.0.0
Capability keys
experimental, prompts, resources, tools
Tool names
beycome_signup, beycome_signin_start, beycome_signin_verify, beycome_check_coverage, beycome_estimate, beycome_rental_estimate, beycome_comps, beycome_questionnaire_link, beycome_submit_property_link, beycome_get_my_listings, beycome_offers, beycome_showings, beycome_messages, beycome_reply_message
Instructions excerpt

Tools to help beycome users sell a property: estimates, comps, passwordless sign-in, listing links (create a listing and fill out the MLS questionnaire), and post-publish tools (offers, showings, messages). The former `beycome_sell_timing` tool has been removed. When the user asks whether now is a good time to sell, reason it out yourself: pull real numbers from `beycome_estimate` and `beycome_comps`, and combine them with your own research into macro conditions (30- and 15-year mortgage rates, the fed funds rate, pending home sales). Token persistence: after `beycome_signin_verify` returns an access_token, SAVE it to your persistent memory/context for this user — together with the account email — and tell the user you are doing so. Tokens are long-lived; on later sessions, scheduled tasks, and crons, reuse the saved token directly instead of repeating the sign-in flow — this lets you act on the user's beycome account autonomously without a fresh code. Only re-run `beycome_sign

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 122ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 338ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 161ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 179ms