Skip to content
MCPSTAMP
MCP server report

Listing MCP server

com.beycome/listing

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 91 of 100 (grade A), higher than 62.2% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, Gemini and MCP Registry. Not ready for ChatGPT.

Measured facts

Score
91A
Sign-in
No sign-in
Tools listed
14
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 8/14 tools miss an explicit hint: beycome_check_coverage, beycome_estimate, beycome_rental_estimate, beycome_comps, beycome_get_my_listings and 3 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  2. Fails

    GET answers SSE or 405

    get_stream

    Measured No response: timeout after 8000 ms

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  3. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured JSON-RPC error -32602 instead of -32601

    Return JSON-RPC error code -32601 (Method not found) for unknown methods.

14 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, initialize latency, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Human-readable title on every tool, Tool descriptions.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Listing

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.beycome.com%2Fmcp)](https://www.mcpstamp.com/r/com-beycome-listing/)

HTML

<a href="https://www.mcpstamp.com/r/com-beycome-listing/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.beycome.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

List on MLS, sell, show, compare and close your real estate property on beycome.
Registry name
com.beycome/listing
Remote URL
https://mcp.beycome.com/mcp
Version
1.0.0
Source
github.com/beycome/mcp.beycome.com
Website
www.beycome.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026