speeron-next
Server Details
Speeron NEXT Digital Guest Journey MCP server (remote HTTP endpoint).
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 1/5 across 4 of 4 tools scored.
The tools have mostly distinct purposes: check_in_user handles user check-ins, confirm_booking manages booking confirmations, search_room_options and search_rooms_by_area both search for rooms but with different filters (general options vs. area-based). There is some overlap between the two search tools, but their names suggest enough differentiation to avoid major confusion.
All tool names follow a consistent verb_noun pattern with snake_case: check_in_user, confirm_booking, search_room_options, search_rooms_by_area. This makes them predictable and easy to understand at a glance.
With 4 tools, the count is borderline for a hotel/booking domain. It covers basic search and check-in/confirmation functions but feels thin, as it lacks tools for actions like booking creation, cancellation, or user management, which might be expected in a complete system.
The tool set has significant gaps for a hotel booking domain. It includes search and check-in/confirmation but misses core operations like create_booking, cancel_booking, update_booking, or manage_user. This incomplete coverage will likely cause agent failures when trying to handle full booking workflows.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
AlicenseBqualityBmaintenanceMCP server for the Hostkit API, enabling management of properties, reservations, guests, invoices, and other property operations.36MIT- Flicense-qualityBmaintenanceMCP server that exposes the Vikey API for reservation management, property listing, and payment information retrieval.
- AlicenseBqualityDmaintenanceThis MCP server provides comprehensive access to the Mews hospitality platform API, covering customer and company management, reservation operations, financial transactions, account management, configuration settings, and services inventory. It implements the core functionality needed for hospitalit538MIT
- Flicense-qualityBmaintenanceRemote MCP server for verifying API key authentication header propagation and debugging inbound HTTP headers.