Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ticketglide Ticketing Agent

REMOTE · TICKETGLIDE.COM

TicketGlide travel comparison and tickets: attraction and day-trip guides and tailored search links.

Available components

66 Trust /100

Last scanned (8 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 256 tokens (~85/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 0
    • Tool “read_guide” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 17 Oct 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://ticketglide.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.ticketglide.com CN=Amazon RSA 2048 S20,O=Amazon,C=US 4 Oct 2026 20 Apr 2027 RSA 2048 SHA256-RSA 414f47cf805b6695995bd76c1618b08e
SANs: *.ticketglide.com, ticketglide.com
CN=Amazon RSA 2048 S20,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 8 Jul 2026 7 Jul 2029 RSA 2048 SHA256-RSA b95efa916a4e6cff9d8348f039fd125b981b5bd
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ticketglide.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
ticketglide.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ticketglide.com/api/mcp Verified 200
http (plaintext) http://ticketglide.com/api/mcp HTTPS enforced 301 https://ticketglide.com/api/mcp
MCP tools · 3 exposed · ~200 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_search_link ~85

Build a TicketGlide website search URL. Destination is a supported destination ID/name or worldwide. Categories include all, attractions, tours and day-trips. This does not execute a search or check availability.

NameTypeReqDescription
categorystring––
currencystring––
destinationstring––
localestring––
querystring––

No output schema declared.

No examples provided.

read_guide ~57

Read a published guide path from search_guides, including source links and factual check dates when present. No drafts or supplier reviews. TicketGlide MCP documentation: https://ticketglide.com/mcp.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

search_guides ~58

Find published TicketGlide city, attraction and day-trip guides. Searches editorial metadata, not supplier inventory.

NameTypeReqDescription
limitinteger––
localestring––
offsetinteger––
querystring––

No output schema declared.

No examples provided.

Install

How do I install the Ticketglide Ticketing Agent MCP server?

Ticketglide Ticketing Agent is a hosted endpoint at https://ticketglide.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ticketglide.com

# add to Claude Code
claude mcp add --transport http com-ticketglide-travel-guides 'https://ticketglide.com/api/mcp'
Common questions

What is the Ticketglide Ticketing Agent MCP server?

Ticketglide Ticketing Agent is an MCP server listed in the public MCP registry as com.ticketglide/travel-guides. TicketGlide travel comparison and tickets: attraction and day-trip guides and tailored search links. This page covers its hosted endpoint (https://ticketglide.com/api/mcp).

Is the Ticketglide Ticketing Agent MCP server safe to use?

Ticketglide Ticketing Agent scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Ticketglide Ticketing Agent MCP server expose?

Ticketglide Ticketing Agent exposes 3 tools: search_guides, read_guide, create_search_link. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.

Does the Ticketglide Ticketing Agent MCP server require authentication?

No. We connected to Ticketglide Ticketing Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ticketglide Ticketing Agent MCP server still maintained?

Ticketglide Ticketing Agent is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.