eventbrite-mcp: Instructions file for Claude Code

CLAUDE.md

eventbrite-mcp CLAUDE.md is an instructions file for Claude Code from chrischall/eventbrite-mcp. It costs 640 tokens per session, scanned A, original, MIT.

Repository-specific instructions for an Eventbrite MCP server, a service that lets an AI agent work with Eventbrite data and events.

In plain words
What is it for?
Use them when developing or debugging this repository's Eventbrite search, event lookup, API fallback, and CSRF-protected requests.
Why use it?
They keep implementation details in one place, including which API route to use, how authentication works, and when to use the browser bridge.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is chrischall/eventbrite-mcp's own configuration. It tells Claude Code how to work on eventbrite-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything eventbrite-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to chrischall/eventbrite-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.

Copy the file
curl -O https://raw.githubusercontent.com/chrischall/eventbrite-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/chrischall/eventbrite-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for eventbrite-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/chrischall/eventbrite-mcp/claude-md.svg)](https://agentmods.dev/instructions/chrischall/eventbrite-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/chrischall/eventbrite-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/eventbrite-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 640 This file is loaded in full into every session.
When invoked 640 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00640 $0.00640
Opus 5 $0.00320 $0.00320
Sonnet 5 $0.00128 $0.00128
Haiku 4.5 $0.00064 $0.00064

Measured 7d ago against content hash d5146f951474, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

eventbrite-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 7d 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.

CLAUDE.md · 40 lines

What it actually says

eventbrite-mcp

MCP server for Eventbrite. Facts specific to THIS repo (fleet-wide conventions live in ~/.claude/CLAUDE.md and the mcp-fleet-builder skill — don't restate them here):

  • Two surfaces, one preferred route. src/client.ts = documented API (eventbriteapi.com/v3, bearer EVENTBRITE_TOKEN, deferred config error). The documented host also serves the consumer discovery API: POST /destination/search/ and GET /events/?event_ids= both answer 200 to a plain bearer token (private OR public) — no WAF, no CSRF, no cookies (verified live 2026-07-30). src/discovery.ts therefore calls the API FIRST and falls back to src/transport-fetchproxy.ts (the bridge, port 37149) only when there is no token or the API refuses. Browse pages (/d/<slug>/events/) are likewise reachable by a plain server-side GET.
  • Search POST needs CSRF: X-CSRFToken = the csrftoken cookie (read via the bridge's read_cookies capability) + X-Requested-With: XMLHttpRequest. GETs are exempt. On a CSRF Failed 401, re-read the cookie and retry once (already implemented in DiscoveryClient.search).
  • Cookie scope must stay in the FIRST pairing declaration (createBootstrapOpts in transport-fetchproxy.ts) — Transporter cannot widen scope after the initial pair approval; changing declared scopes forces a full re-pair (profile remove/re-add on the fpx CLI side).
  • Place ids: searches take Whosonfirst-style ids, resolved by grepping "placeId" from the SSR bytes of /d/<slug>/events/ (a direct fetch — no bridge). There is no API endpoint for this: /destination/places/, /places/ and /destination/autocomplete/ all 404. Never guess ids; never call the site's Google Places autocomplete. Free-text locations become candidate slugs via slugCandidates; a bare city yields none by design.
  • Never call /destination/search/log_requests/ or /log_engagement/ (site telemetry).
  • All request/response shapes are pinned in docs/EVENTBRITE-API.md with their verification status — keep that file's status notes truthful when endpoints change, and re-capture before coding new ones.
  • registerDiscoveryTools takes the fetchproxy bridge or null. With null it registers the API-route discovery tools but skips eb_healthcheck, which diagnoses the bridge and has nothing to report without one.
  • Version lives in src/version.ts alone (single x-release-please-version marker); index.ts imports it.
Changes

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.

  1. 7d ago First seen · 40 lines · 640 tokens per session scan A d5146f951474

Subscribe to this mod's changes

eventbrite-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/eventbrite-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 640 tokens to every session, about $0.0032 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens