Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

app.g-guest/g-guest

REMOTE · G-GUEST.APP

Book a table, appointment or class at a real local business. Instant confirmation, no API key.

Available components

0 this week 76 Trust /100

Last scanned (16 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1256 tokens (~157/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Oct 26 0
    • Tool “check_booking” rewrote its description, which is the text the model reads security
    • Tool “create_booking” rewrote its description, which is the text the model reads security
  • 29 Sept 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://g-guest.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=g-guest.app CN=YR2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 RSA 2048 SHA256-RSA 562ea0b9bd1d4f754029024cd55f04191b6
SANs: g-guest.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of g-guest.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
g-guest.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://g-guest.app/api/mcp Verified 200
http (plaintext) http://g-guest.app/api/mcp HTTPS enforced 308 https://g-guest.app/api/mcp
MCP tools · 8 exposed · ~1,145 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_booking ~171

Cancel an upcoming booking and release its slot to other guests. Identified like check_booking: booking_id plus manage_token. Confirm with the guest before calling; the cancellation is immediate and this server cannot undo it, the guest would simply book again. The venue is notified exactly as for a cancellation from the manage link. Safe to retry: cancelling a booking that is already cancelled returns the same result, not an error. A booking whose start time has passed cannot be cancelled and returns an error saying so. To move a booking to another time, cancel it and create a new one.

NameTypeReqDescription
booking_idstringyesThe booking_id create_booking returned, or the id in the guest's manage link.
manage_tokenstringyesThe token from the same booking's manage link (its ?token= parameter).

No output schema declared.

No examples provided.

check_availability ~67

List bookable time slots for a business on a given date and party size. Offer the guest only slots where available is true.

NameTypeReqDescription
datestringyesYYYY-MM-DD, in the venue's local calendar.
party_sizeintegeryes–
slugstringyes–

No output schema declared.

No examples provided.

check_booking ~195

Look up one existing booking so the guest can confirm when and where it is. Identify it with the booking_id and manage_token that create_booking returned; both also sit in the guest's confirmation email as the manage link, /booking/<booking_id>?token=<manage_token>. Returns the business, the local date and time with its timezone, party size, service and status: confirmed, pending_confirmation, pending_payment (with payment_url while it can be paid), cancelled, or for past bookings completed or no_show. Never returns the guest's name, email or phone. A wrong or missing token is refused without revealing whether the booking exists.

NameTypeReqDescription
booking_idstringyesThe booking_id create_booking returned, or the id in the guest's manage link.
manage_tokenstringyesThe token from the same booking's manage link. If the guest only has the link, take the token from its ?token= parameter.

No output schema declared.

No examples provided.

create_booking ~277

Create a real reservation. Use a start value returned by check_availability. Never invent guest details. Ask the person for their real name, email and phone first. If the result status is pending_confirmation, show the guest the confirmation_url. If it is pending_payment, the venue takes a prepayment: show the guest the payment_url, and do not say it is booked until it is paid.

NameTypeReqDescription
emailstringyes–
idempotency_keystring–Retry safety: pick any unique string for this booking attempt and reuse it on retries. The same key always returns the same booking, never a duplicate.
languagestring–The guest's language as an ISO 639-1 code: en, nl, de, fr, es, it, id or bg. The confirmation, the reminders and the manage page are sent in it. Defaults to English.
namestringyes–
notesstring––
party_sizeintegeryes–
phonestringyes–
slugstringyes–
sourcestring–Which assistant is booking. Defaults to other_ai. proof_video is our own channel: bookings made while filming a proof clip.
startstringyesThe slot's `start` value, copied exactly as check_availability returned it.

No output schema declared.

No examples provided.

fetch ~36

Fetch full details for one business id returned by search: services, hours, timezone and how to book it.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_business ~53

Look up a business on G-Guest: services, opening hours, timezone and maximum party size. Call this first if you only know the slug.

NameTypeReqDescription
slugstringyesBusiness identifier, e.g. "demo".

No output schema declared.

No examples provided.

request_listing ~306

Ask G-Guest to list a business that is not on it yet. Use it when the person you are helping runs a restaurant, cafe, bar, salon, spa, studio or clinic and wants reservations that assistants can make. Nothing is published by this call: the request reaches the G-Guest team as a lead, a person reviews it and contacts the business, and only then is anything set up. The owner's or manager's email is required, because the reply comes by email; a phone is optional extra. Do not call it for a guest who merely wants to book somewhere, and never submit a business without its owner's or manager's say-so. Returns a receipt with a reference id; no timeline is promised.

NameTypeReqDescription
business_namestringyesThe business's own name, as its owner writes it.
business_typestringyesThe closest category.
citystringyesCity and country, e.g. "Canggu, Indonesia".
contact_emailstringyesEmail of the owner or manager who asked. The reply goes here.
contact_namestring–Who asked, so the reply can address them by name.
contact_phonestring–Phone with country code, optional.
messagestring–Anything the owner wants the team to know: languages, seats, how bookings are taken today. Up to 500 characters.
websitestring–The business website or Instagram page, if it has one.

No output schema declared.

No examples provided.

search ~40

Search bookable businesses on G-Guest by name or slug. Returns ids you can pass to fetch or to the booking tools.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the app.g-guest/g-guest MCP server?

app.g-guest/g-guest is a hosted endpoint at https://g-guest.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · g-guest.app

# add to Claude Code
claude mcp add --transport http app-g-guest-g-guest 'https://g-guest.app/api/mcp'
Common questions

What is the app.g-guest/g-guest MCP server?

app.g-guest/g-guest is an MCP server listed in the public MCP registry as app.g-guest/g-guest. Book a table, appointment or class at a real local business. Instant confirmation, no API key. This page covers its hosted endpoint (https://g-guest.app/api/mcp).

Is the app.g-guest/g-guest MCP server safe to use?

app.g-guest/g-guest scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the app.g-guest/g-guest MCP server expose?

app.g-guest/g-guest exposes 8 tools: search, fetch, get_business, check_availability, create_booking, and 3 more. Their descriptions and schemas cost roughly 1,145 tokens of context every time the server is loaded.

Does the app.g-guest/g-guest MCP server require authentication?

No. We connected to app.g-guest/g-guest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the app.g-guest/g-guest MCP server still maintained?

app.g-guest/g-guest is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the app.g-guest/g-guest MCP server?

VerifyMCP ran 12 checks on app.g-guest/g-guest, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about app.g-guest/g-guest: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.