Skip to content

g-guest MCP server

app.g-guest/g-guestg-guest.appstreamable-httpv1.0.1Scanned

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

8 tools: 1 can delete or cancel things, 3 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the g-guest MCP server can do

The g-guest MCP server is published by g-guest.app, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: cancel_booking) and create or change data (3 tools: create_booking, check_booking and request_listing). 4 tools only read.

1 tool can send data out of your system (create_booking).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 1Claude Code: deny
  • cancel_bookingCancel an upcoming booking and release its slot to other guests.No findings

    Why it is in this group

    • The name "cancel_booking" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    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.
Changes things 3Claude Code: ask
  • check_bookingLook up one existing booking so the guest can confirm when and where it is.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • create_bookingCreate a real reservation.Can send data outNo findings

    Why it is in this group

    • The name "create_booking" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.
  • request_listingAsk G-Guest to list a business that is not on it yet.No findings

    Why it is in this group

    • The name "request_listing" says "request": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • check_availabilityList bookable time slots for a business on a given date and party size.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List bookable time slots for a business on a given date and party size. Offer the guest only slots where available is true.
  • fetchFetch full details for one business id returned by search: services, hours, timezone and how to book it.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch full details for one business id returned by search: services, hours, timezone and how to book it.
  • get_businessLook up a business on G-Guest: services, opening hours, timezone and maximum party size.No findings

    Why it is in this group

    • The name "get_business" says "get": a word for reading.
    Description, as the server wrote it
    Look up a business on G-Guest: services, opening hours, timezone and maximum party size. Call this first if you only know the slug.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://g-guest.app/api/mcp: tools/list returned 8 tools to an anonymous client, including cancel_booking (destructive), create_booking (write), check_booking (write), request_listing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http g-guest https://g-guest.app/api/mcp
claude mcp add --transport http g-guest https://g-guest.app/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__g-guest__search",
      "mcp__g-guest__fetch",
      "mcp__g-guest__get_business",
      "mcp__g-guest__check_availability"
    ],
    "ask": [
      "mcp__g-guest__create_booking",
      "mcp__g-guest__check_booking",
      "mcp__g-guest__request_listing"
    ],
    "deny": [
      "mcp__g-guest__cancel_booking"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as g-guest. Review it before you use it.

Capability tags behind 1 rule
  • mcp__g-guest__create_booking outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.g-guest/g-guest/verify?hash=ffc2adc4ca2a387d2a104e1510be16418fb226c2be070961f25e1c9df01b18d2" | jq -e '.changed == false'

Pinned hash ffc2adc4ca2a, from Nov 12, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.g-guest/g-guest/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.g-guest/g-guest
[![Anlyon Radar](https://radar.anlyon.com/badge/app.g-guest/g-guest.svg)](https://radar.anlyon.com/servers/app.g-guest/g-guest)

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

g-guest MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the g-guest MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the g-guest MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_booking.

Can the g-guest MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the g-guest MCP server have?

8 tools: 1 destructive, 3 write, 4 read. cancel_booking, create_booking, check_booking, request_listing, search, fetch, get_business and check_availability.

Does the g-guest MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the g-guest MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_booking.

Has the g-guest MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.