com.beycome/listing vs Mashvisor MCP Server and API by Cotlet
com.beycome/listing is an MCP server published by beycome.com. Marketplaces we read that list it: 1 (Official MCP Registry). Mashvisor MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.beycome/listing |  Mashvisor MCP Server and API by Cotlet |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.2 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.beycome/listing | Mashvisor MCP Server and API by Cotlet |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | Remote server (mcp.beycome.com/mcp) | Remote server (cotlet.dev/mcp/v1/mashvisor/connect) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/beycome/mcp.beycome.com | Not stated |
| Changes in the last 7 days (differs) | 0 | 7 |
| First seen (differs) | 2026-10-11 | 2026-11-09 |
| Endpoint at the last check (differs) | Status out of date: last check 32 h ago returned HTTP 406 | Answered with HTTP 302 (13 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.beycome/listing
List on MLS, sell, show, compare and close your real estate property on beycome.
Mashvisor MCP Server and API by Cotlet
Mashvisor rental property investment analytics MCP server: run saved search, get property analysis.
How to run each
com.beycome/listing As a remote MCP server
claude mcp add --transport http listing https://mcp.beycome.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Mashvisor MCP Server and API by Cotlet As a remote MCP server
claude mcp add --transport http mashvisor https://cotlet.dev/mcp/v1/mashvisor/connectCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of com.beycome/listing responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: com.beycome/listing · What it can do: Mashvisor MCP Server and API by Cotlet · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.