Borrowing it
Nothing to install: this file belongs to tickadoo/tickadoo-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tickadoo/tickadoo-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/tickadoo/tickadoo-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/tickadoo/tickadoo-mcp/claude-md)<a href="https://agentmods.dev/instructions/tickadoo/tickadoo-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/tickadoo/tickadoo-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01790 | $0.01790 |
| Opus 5 | $0.00895 | $0.00895 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
tickadoo-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
CLAUDE.md — tickadoo-mcp
This file is read automatically by Claude Code at session start. Lightweight project doc; defers to AGENTS.md for the shared AI-agent coordination conventions and to the HowardOS repo (github.com/tickadoo/howard → CLAUDE.md) for the broader tickadoo project context (architecture, deploy workflows, environment variables, supplier integrations, team, Slack IDs, etc.).
What is this repo?
@tickadoo/mcp-server — the npm distribution of the public tickadoo MCP (Model Context Protocol) server. It surfaces 23 tools over 13,090 products in 681 cities to AI agents (ChatGPT, Claude, Perplexity, etc.) so they can search, browse, recommend, and book tickadoo experiences on behalf of end users. Installed by clients from the MCP Marketplace / npm, or used directly over Streamable HTTP at https://mcp.tickadoo.com/mcp.
Since v2.0.0 this package is a thin remote bridge (GRO-573): the npm command is a stdio transport that proxies to the canonical remote server. It no longer defines tools, formats catalogue data, or calls a backend directly. The remote owns the tool list, schemas, results, and errors. The remote MCP server (and the embeddable widget bundle) now live in the HowardOS repo (github.com/tickadoo/howard), which is canonical (GRO-574).
Agent-intelligence layer (served by the remote): search tools carry _best_picks, _price_tiers, _group_summary, _conversation_starters, _available_filters, _related_searches, _next_step; details tools carry _booking_urgency, _cross_sell, _intent_token, _accessibility.
Architecture at a glance
- Runtime: TypeScript stdio bridge
src/index.ts→src/bridge.ts— local stdio transport (shipped on npm as@tickadoo/mcp-server) that proxiestools/list,tools/call,resources/list,resources/read, andpingto the remote.src/config.ts— bridge config (remote URL viaTICKADOO_MCP_URL, log level viaTICKADOO_LOG_LEVEL).
- Canonical remote:
https://mcp.tickadoo.com/mcp— served and deployed from the howard repo, not this one. This repo does not deploy a Cloudflare Worker. - Build:
npm run build→dist/index.js(esbuild bundle for stdio/npm). - Registry metadata:
server.jsonis refreshed from the live remote vianpm run sync:server-json. - Skills (
skills/*/SKILL.md, PR #96): 7 skills for Agent Plugins clients and the OpenAI Plugin Directory (a plugin = our MCP server + optional Skills for complex workflows) — thetickadoo-experiencesdiscovery skill (mirrored to.claude/skills/; keep the two copies in sync) plus 6 workflow skills (plan-a-trip,family-day-out,tonight-and-last-minute,date-night,compare-before-you-book,near-a-landmark). Ground every tool reference inserver.json; frontmatternamemust match the folder. BAC-779 adds them to the npm published file set and verifies the exact tarball; OpenAI still snapshots uploaded or MCP-imported skills during its Platform submission flow. - Testing: vitest (
npm test);LIVE=1 npm testruns the optional live integration test against the remote. - No API key required. Customer never sees supplier names; everything is presented as tickadoo.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 80 lines · 1,790 tokens per session scan A a225e831e1e4
tickadoo-mcp CLAUDE.md is an instructions file published in the GitHub repository tickadoo/tickadoo-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 1,790 tokens to every session, about $0.0089 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.