io.github.tickadoo/tickadoo-mcp

MCPcommunity
v1.3.0io.github.tickadooUnknownUpdated 4mo agoGitHub

Search and book theatre, attractions, tours across 681 cities. 13,090+ products.

is the local stdio entrypoint for tickadoo MCP. Since v2.0.0 it is a thin bridge to the canonical remote server at: The package no longer defines tools, formats catalogue data, or calls a local tickadoo backend. It connects to the remote Streamable HTTP MCP server and proxies , , , , and . The live remote owns the tool list, schemas, results, and errors. No API key is required. Use the hosted…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.tickadoo
LicenseUnknown
Version1.3.0
Sourcemcp-registry
GitHubtickadoo/tickadoo-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface3 tools · none privileged
Security scan✓ CleanvHEAD · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

is the local stdio entrypoint for tickadoo MCP. Since v2.0.0 it is a thin bridge to the canonical remote server at: The package no longer defines tools, formats catalogue data, or calls a local tickadoo backend. It connects to the remote Streamable HTTP MCP server and proxies , , , , and . The live remote owns the tool list, schemas, results, and errors. No API key is required. Use the hosted remote directly when your MCP client supports Streamable HTTP: Use the npm package when your MCP client…

Keywords
mcp