C+

guesty-mcp-server.vercel.app

Item: guesty-mcp-server.vercel.app
Rating: 77
Author: wmcp.sh

https://guesty-mcp-server.vercel.app/mcp

77/100 · MCP Trust Grade · checked 3h ago · MCP 2024-11-05

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 43 tools · Developer Tools

list_reservations

Guesty list reservations operation

get_reservation

Guesty get reservation operation

create_reservation

Guesty create reservation operation

update_reservation

Guesty update reservation operation

list_listings

Guesty list listings operation

get_listing

Guesty get listing operation

update_listing

Guesty update listing operation

list_listing_calendar

Guesty list listing calendar operation

update_calendar_availability

Guesty update calendar availability operation

update_calendar_pricing

Guesty update calendar pricing operation

get_guest

Guesty get guest operation

list_guests

Guesty list guests operation

search_guests

Guesty search guests operation

list_conversations

Guesty list conversations operation

get_conversation_posts

Guesty get conversation posts operation

send_message

Guesty send message operation

get_financial_summary

Guesty get financial summary operation

list_owner_payouts

Guesty list owner payouts operation

+25 more tools

Spec conformance20%100

✓ initialize → protocolVersion 2024-11-05
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 43 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

43 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%84

single-probe latency 861ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%0

0% of tools have typed inputSchema
0/43 declare outputSchema
8 destructive-by-name tools lack safety annotations

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2024-11-05

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade guesty-mcp-server.vercel.app on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — guesty-mcp-server.vercel.app grade C+

Share on X Open card image

https://wmcp.sh/mcp/grade/guesty-mcp-server.vercel.app

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C+](https://wmcp.sh/mcp/grade/guesty-mcp-server.vercel.app/badge.svg)](https://wmcp.sh/mcp/grade/guesty-mcp-server.vercel.app)

HTML

<a href="https://wmcp.sh/mcp/grade/guesty-mcp-server.vercel.app"><img src="https://wmcp.sh/mcp/grade/guesty-mcp-server.vercel.app/badge.svg" alt="MCP Trust Grade C+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.