Hopper MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool has a distinct purpose: booking flights/hotels, retrieving bookings, forecasting prices, searching flights/hotels, and setting alerts. No overlap exists; for example, search_flights and book_flight are clearly separate operations, and get_price_forecast focuses on predictions rather than actions.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., book_flight, search_hotels, set_price_alert). The verbs are descriptive and aligned with the actions, and there are no deviations in style or convention across the set.
Tool Count5/5
With 7 tools, the server is well-scoped for travel booking and price management. Each tool serves a clear function in the workflow, from search and forecast to booking and alerts, without being overly sparse or bloated.
Completeness5/5
The tool set provides complete coverage for the travel booking domain: search (flights/hotels), forecast (prices), booking (flights/hotels), management (view bookings), and alerts (price drops). No obvious gaps exist, as it supports the full lifecycle from research to post-booking monitoring.
Average 3.8/5 across 7 of 7 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, description carries full burden. It effectively discloses return contents (ratings, amenities, buy/wait recommendation) since no output schema exists. However, fails to declare safety characteristics (read-only/non-destructive) or operational constraints like rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences with zero waste. First sentence establishes purpose and unique value prop (price predictions); second sentence details return value. Perfectly front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Appropriately complete for a 7-parameter search tool with full schema coverage. Compensates for missing output schema by detailing return fields. Minor gap: lacks explicit read-only declaration expected in absence of annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% description coverage with clear examples (date formats, defaults). Description adds no additional parameter-specific semantics, but baseline 3 is appropriate given schema completeness.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb 'Search' and resource 'hotels on Hopper'. Distinguishes from generic search via 'price predictions' and specific platform mention. Lacks explicit distinction from sibling 'book_hotel' (browse vs purchase workflow), preventing a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no guidance on when to use this tool versus siblings like 'book_hotel' (search first, then book) or 'get_price_forecast' (direct forecast vs hotel listing with forecast). No prerequisites or exclusions stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Adds valuable context about post-booking behavior (Price Drop Guarantee) and implies financial/sensitive data handling, but omits idempotency, cancellation policy, return value structure, or error states for this destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with clear front-loading of core action. Efficient structure, though the Price Drop Guarantee sentence provides platform context rather than tool behavior, slightly diluting focus.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for basic invocation but incomplete for a financial transaction tool: lacks description of return values (confirmation data, errors), auth requirements, or modification capabilities given zero annotations and no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, establishing baseline 3. Description adds semantic grouping ('guest details and payment information') but does not extend individual parameter semantics beyond what schema already documents (e.g., no format examples for payment_method).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States specific verb ('Initiate') + resource ('hotel booking') + platform ('Hopper'), clearly distinguishing from siblings like 'search_hotels' (query vs. transaction) and 'book_flight' (different resource).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies prerequisites via 'Requires guest details and payment information,' indicating when the tool is ready to use, but lacks explicit comparison to siblings (e.g., 'Use search_hotels first to obtain hotel_id').
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Adds valuable behavioral context by mentioning 'authentication requirements' as a possible return state, implying multi-step flow. However, misses critical safety context for a financial transaction: no mention of idempotency, payment failure handling, immediate vs. deferred charging, or reversibility.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with zero waste. Front-loaded with core action ('Initiate a flight booking...'), followed by prerequisites and return value. Every sentence earns its place; no redundant or filler text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a 6-parameter booking tool with no output schema: compensates by describing return values ('booking confirmation or authentication requirements'). However, gaps remain for a financial transaction tool: missing error scenarios, pricing disclosure, cancellation policies, and explicit destructive/financial risk warnings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% description coverage, establishing baseline of 3. Description adds high-level grouping ('passenger details and payment information') but no additional semantic value regarding parameter relationships, validation rules, or format constraints beyond what the schema already documents.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Excellent specificity: 'Initiate a flight booking on Hopper for a specific flight' provides clear verb (initiate), resource (flight booking), platform (Hopper), and scope. Clearly distinguishes from sibling search_flights (booking vs. searching) and book_hotel (flight vs. hotel).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides prerequisite hints ('Requires passenger details and payment information') and expected outcomes ('Returns booking confirmation or authentication requirements'), but lacks explicit sequencing guidance (e.g., 'Use after search_flights') or exclusion criteria (when not to attempt booking).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, description carries burden of disclosing return structure—succeeds by specifying 'flight and hotel booking history with status, itinerary details, and pricing'. However, omits safety indicators (read-only/idempotent), rate limits, or authentication requirements beyond the email parameter.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficiently structured sentences: first states purpose, second discloses return payload. Zero redundancy despite lack of output schema—every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 2-parameter retrieval tool without output schema, description adequately compensates by describing return contents (status, itinerary, pricing). Could improve by noting error conditions (e.g., invalid email) or pagination behavior, but sufficient for agent invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear descriptions for both 'email' and 'booking_type'. Description adds no parameter-specific guidance, but baseline 3 is appropriate since schema fully documents inputs without need for elaboration.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'View' with clear resource 'bookings from a Hopper account'. Distinctly positions this as a retrieval tool versus sibling actions like 'book_flight', 'book_hotel' (creation) and 'search_flights', 'search_hotels' (discovery).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage through 'current and past bookings' (history retrieval) versus booking new travel, but lacks explicit when-to-use guidance or prerequisites (e.g., 'use after booking confirmation' or 'requires active account').
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full disclosure burden. It successfully conveys behavioral traits: 'real-time pricing' indicates live data, 'AI-powered price predictions' discloses algorithmic processing, and 'buy/wait/watch recommendations' explains the decision-support output format. Missing only operational details like rate limits or no-results behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. First sentence front-loads core function and unique differentiators (AI predictions). Second sentence compensates for missing output schema by describing return structure. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema exists, the description appropriately describes return values ('flight options with buy/wait/watch recommendations'). With 6 well-documented parameters and high complexity, the description provides sufficient context for agent selection, though could mention one-way vs round-trip handling implied by optional return_date.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with all 6 parameters fully documented (IATA formats, date syntax, enum values). The description correctly does not duplicate this information, maintaining baseline score. No additional semantic constraints (e.g., date range limits) are provided in description, but none are required given schema completeness.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'Search' with clear resource 'flights' and platform 'Hopper'. It distinguishes from sibling 'book_flight' by emphasizing this returns options rather than completing a transaction, and differs from 'search_hotels' via the flight-specific context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies workflow by stating it 'Returns flight options', suggesting this precedes booking, but lacks explicit when-to-use guidance versus 'get_price_forecast' or 'set_price_alert'. It establishes unique value (AI predictions, buy/wait/watch recommendations) but doesn't state exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and successfully explains the asynchronous notification behavior ('Hopper will notify via the app/email when...'). It clarifies trigger conditions (target price hit or optimal window opening) but omits alert persistence duration, cancellation methods, and authentication requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two well-structured sentences with zero waste: first states the action and scope, second explains the behavioral outcome. Information is front-loaded with the core purpose immediately clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the straightforward parameter schema (flat structure, 100% coverage) and lack of output schema, the description adequately covers the core user journey. It could improve by noting the optional nature of 'origin' for flight alerts or what the tool returns upon creation, but it sufficiently explains the value proposition and operational flow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, establishing a baseline of 3. The description adds context by mentioning 'Hopper' and the notification mechanism but does not expand on parameter semantics beyond what the schema already provides (e.g., doesn't clarify that 'origin' is optional despite being a flight parameter, or explain the IATA code format constraints).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb ('Create') and clear resource ('price drop alert'), explicitly scoping to 'flight or hotel' which distinguishes it from sibling booking tools (book_flight, book_hotel) and search tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
While the description explains the tool's function, it lacks explicit guidance on when to use this versus immediate booking (book_flight/hotel) or checking forecasts (get_price_forecast). Usage is implied ('wait for price drops') but no prerequisites or alternative comparisons are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Compensates by disclosing return value structure: categorical recommendation (buy/wait/watch), confidence percentage, and reasoning. Lacks operational details like rate limits or caching, but covers the critical behavioral trait of what the forecast contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. Front-loaded action ('Get...') followed immediately by return value specification. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 100% schema coverage and no output schema, description adequately compensates by explaining return values. Missing only forecast horizon/validity window details. Sufficient for agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameters are fully documented in structured fields. Description implicitly references trip_type via 'flight or hotel' but adds no semantic detail beyond schema (no examples, formats, or conditional logic explanations). Baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb 'Get' + resource 'AI price forecast' + clear domain 'flight or hotel'. Distinguishes from siblings (search_flights, book_flight, set_price_alert) by emphasizing predictive analytics rather than search, booking, or alerts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage context ('whether to buy now, wait...') which signals this is for purchase timing decisions. However, lacks explicit when-not-to-use guidance or comparison to set_price_alert for ongoing monitoring vs one-time forecasts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![mcp-hopper MCP server](https://glama.ai/mcp/servers/markswendsen-code/mcp-hopper/badges/card.svg)](https://glama.ai/mcp/servers/markswendsen-code/mcp-hopper)

Score Badge

Copy to your README.md:

[![mcp-hopper MCP server](https://glama.ai/mcp/servers/markswendsen-code/mcp-hopper/badges/score.svg)](https://glama.ai/mcp/servers/markswendsen-code/mcp-hopper)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markswendsen-code/mcp-hopper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server