Tixxly MCP server — connect AI agents to tours, experiences, and activities
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TIXXLY_API_KEYAPI keyrequiredTixxly vendor API key (created from admin dashboard with mcp group)
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
experiences_availabilityCheck availability for a specific experience on given dates.Check availability for a specific experience on given dates.
No input schema was published for this tool.
booking_confirmConfirm a reservation and capture the payment. Call this after the customerConfirm a reservation and capture the payment. Call this after the customer
No input schema was published for this tool.
booking_reserveCreate a booking reservation. Returns payment_url for the user to complete payment.Create a booking reservation. Returns payment_url for the user to complete payment.
No input schema was published for this tool.
booking_optionsGet booking form questions for contact details and passengers.Get booking form questions for contact details and passengers.
No input schema was published for this tool.
booking_statusCheck the current status of a reservation. Returns reservation details,Check the current status of a reservation. Returns reservation details,
No input schema was published for this tool.
experiences_detailGet full details of a specific experience including description, pricing categories,Get full details of a specific experience including description, pricing categories,
No input schema was published for this tool.
experiences_searchSearch for tours, activities, and experiences available through Tixxly.Search for tours, activities, and experiences available through Tixxly.
No input schema was published for this tool.
booking_flowStep-by-step guide for the Tixxly booking flowStep-by-step guide for the Tixxly booking flow
No input schema was published for this tool.
supported_categoriesList of supported experience categories for search filteringList of supported experience categories for search filtering
No input schema was published for this tool.
book_experienceGuided flow to search, check availability, and book a travel experienceGuided flow to search, check availability, and book a travel experience
No input schema was published for this tool.
locationDestination city or regionDestination city or region
No input schema was published for this tool.
activityType of experience (e.g., 'sunset sailing', 'food tour')Type of experience (e.g., 'sunset sailing', 'food tour')
No input schema was published for this tool.
explore_destinationDiscover what tours and activities are available in a destinationDiscover what tours and activities are available in a destination
No input schema was published for this tool.
13 of 13 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Tixxly MCP server — connect AI agents to tours, experiences, and activities
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
81 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+69 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.