Data Collection

beycome.com

Provides user authentication and property estimation services for a real estate platform.

1 endpoint14 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.beycome.com/mcp

No auth detected

MCP server metadata

Name: com.beycome/listing
Version: 1.0.0

Capabilities

experimentalprompts.listChangedresources.listChangedtools.listChanged

Server instructions

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_signin_start` → `beycome_signin_verify` if a tool returns 401 (token revoked or expired), then save the new token.

Known tools 14

beycome_signup

Account stage — register a new beycome user (POST /auth/register).

Potential side effects

beycome_signin_start

Account stage — send a one-time sign-in code (POST /auth/check-email).

Potential side effects

beycome_signin_verify

Account stage — exchange the one-time code for the access_token (POST /auth/validate-code).

Potential side effects

beycome_check_coverage

Discovery stage — is this state served by beycome MLS?

Inferred read-only

beycome_estimate

Discovery stage — estimate a property's SALE value (beycome CMA + Zillow Zestimate).

Inferred read-only

beycome_rental_estimate

Discovery stage — estimate a property's monthly RENT (POST /gemini-estimate).

Potential side effects

beycome_comps

Discovery stage — sold comparable listings near a location (GET /comps).

Inferred read-only

beycome_questionnaire_link

Questionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link).

Potential side effects

beycome_submit_property_link

Listing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link).

Potential side effects

beycome_get_my_listings

Recovery stage — the signed-in user's properties (GET /properties).

Inferred read-only

beycome_offers

Post-publish stage — offers received on the owner's listings (GET /offers).

Potential side effects

beycome_showings

Post-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events).

Potential side effects

beycome_messages

Post-publish stage — read the owner's buyer/inquiry messages (GET /messages).

Potential side effects

beycome_reply_message

Post-publish stage — reply to a buyer/inquiry message (POST /messages/reply).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.com-beycome-listing]
url = "https://mcp.beycome.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "com-beycome-listing": {
      "type": "http",
      "url": "https://mcp.beycome.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: com-beycome-listing
Remote MCP URL: https://mcp.beycome.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "com-beycome-listing": {
      "url": "https://mcp.beycome.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "com-beycome-listing": {
      "type": "http",
      "url": "https://mcp.beycome.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "com-beycome-listing",
  "transport": "streamable-http",
  "url": "https://mcp.beycome.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for beycome.com was fetched 2026-07-29T22:08:36.894Z and is being refreshed.

Trust status Trusted

beycome.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.