@chrischall/eventbrite-mcp

MCPattested
v1.1.4Claude CodeMITUpdated 7d agonpmGitHub

Eventbrite MCP server for Claude — developed and maintained by AI (Claude Code)

Works in
ClaudeCursorCopilotGemini

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
792Downloads/wk
7d agoLast update
Reads these credentials
  • EVENTBRITE_TOKENAPI keyoptional

    Personal OAuth token (eventbrite.com/platform/api-keys); needed for account tools

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.

Package
AuthorClaude Code
LicenseMIT
Version1.1.4
Sourcenpm+mcp-registry
npm@chrischall/eventbrite-mcp
GitHubchrischall/eventbrite-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 9029140
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface26 tools · none privileged
Security scan✓ Cleanv0.1.2 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

26 tools · none privileged
Statically extracted from the published packagev0.1.2 · 1mo ago

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.

eb_meNo description published

This tool published no description. Forge does not invent one.

eb_my_ordersNo description published

This tool published no description. Forge does not invent one.

eb_my_organizationsNo description published

This tool published no description. Forge does not invent one.

eb_org_eventsNo description published

This tool published no description. Forge does not invent one.

eb_org_attendeesNo description published

This tool published no description. Forge does not invent one.

eb_org_ordersNo description published

This tool published no description. Forge does not invent one.

eb_org_reportNo description published

This tool published no description. Forge does not invent one.

eb_resolve_placeNo description published

This tool published no description. Forge does not invent one.

eb_search_eventsNo description published

This tool published no description. Forge does not invent one.

eb_event_detailsNo description published

This tool published no description. Forge does not invent one.

eb_eventNo description published

This tool published no description. Forge does not invent one.

eb_ticket_classesNo description published

This tool published no description. Forge does not invent one.

eb_event_descriptionNo description published

This tool published no description. Forge does not invent one.

eb_referenceNo description published

This tool published no description. Forge does not invent one.

eb_event_attendeesNo description published

This tool published no description. Forge does not invent one.

eb_event_attendeeNo description published

This tool published no description. Forge does not invent one.

eb_event_ordersNo description published

This tool published no description. Forge does not invent one.

eb_ticket_classNo description published

This tool published no description. Forge does not invent one.

eb_event_questionsNo description published

This tool published no description. Forge does not invent one.

eb_orderNo description published

This tool published no description. Forge does not invent one.

eb_venueNo description published

This tool published no description. Forge does not invent one.

eb_venue_eventsNo description published

This tool published no description. Forge does not invent one.

eb_organizerNo description published

This tool published no description. Forge does not invent one.

eb_organizer_eventsNo description published

This tool published no description. Forge does not invent one.

eb_series_eventsNo description published

This tool published no description. Forge does not invent one.

eb_userNo description published

This tool published no description. Forge does not invent one.

0 of 26 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.

About

Eventbrite MCP server for Claude — developed and maintained by AI (Claude Code)

Keywords
mcpmodel-context-protocolclaudeaieventbriteeventsticketsevent-discoveryorders
Alternatives
Comparing tool surfaces…

Tools exposed

26 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.