mcp-registry/app.g-guest/g-guest · v1.1.0
As of 2026-10-24 04:16 UTC, the G Guest MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 11 minutes.
Book a table, appointment or class at a real local business. Instant confirmation, no API key.
Claude Code
claude mcp add --transport http g-guest-mcp-server https://g-guest.app/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"g-guest-mcp-server": {
"type": "http",
"url": "https://g-guest.app/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
10 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.g-guest%2Fg-guest/fixes
{
"name": "cancel_booking",
"description": "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 r",
"inputSchema": {
"type": "object",
"required": [
"booking_id",
"manage_token"
],
"properties": {
"booking_id": {
"type": "string",
"description": "The booking_id create_booking returned, or the id in the guest's manage link."
},
"manage_token": {
"type": "string",
"description": "The token from the same booking's manage link (its ?token= parameter)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "check_availability",
"description": "List bookable time slots for a business on a given date and party size. Offer the guest only slots where available is true.",
"inputSchema": {
"type": "object",
"required": [
"slug",
"date",
"party_size"
],
"properties": {
"date": {
"type": "string",
"description": "YYYY-MM-DD, in the venue's local calendar."
},
"slug": {
"type": "string"
},
"party_size": {
"type": "integer",
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_booking",
"description": "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 n",
"inputSchema": {
"type": "object",
"required": [
"booking_id",
"manage_token"
],
"properties": {
"booking_id": {
"type": "string",
"description": "The booking_id create_booking returned, or the id in the guest's manage link."
},
"manage_token": {
"type": "string",
"description": "The token from the same booking's manage link. If the guest only has the link, take the token from its ?token= parameter."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.g-guest/g-guest"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.g-guest/g-guest"}) over MCP.
request_listing ~433 tokenscreate_booking ~405 tokenscheck_booking ~257 tokenscancel_booking ~244 tokenscheck_availability ~114 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.g-guest%2Fg-guest?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.g-guest%2Fg-guest?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.g-guest%2Fg-guest.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.g-guest%2Fg-guest.svg :target: https://glimind.com/server/mcp-registry%2Fapp.g-guest%2Fg-guest?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8e62fa31b41df161…, first seen 2026-10-17, included at leaf 6882 of 56,458. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable data servers · most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 04:16 UTC, the G Guest MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 11 minutes.
G Guest MCP server advertises 8 tools, including cancel_booking, check_availability, check_booking, create_booking, fetch.
Point your MCP client at this streamable-http endpoint: https://g-guest.app/api/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.