Skip to content

Eventzilla MCP by usefulapi

io.usefulapi/eventzillausefulapi.iostreamable-httpv1.27.4Scanned

Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales.

11 tools: 1 can delete or cancel things and 10 only read.

Tools: 1 delete, 0 irreversible, 0 write, 10 read.
  • Reads private data · 1
  • Reads text others write · 11
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Eventzilla MCP by usefulapi can do

The Eventzilla MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: eventzilla_toggle_event_sales). 10 tools only read.

1 tool reads private data (eventzilla_list_users); 11 tools bring in text other people can write (eventzilla_list_events, eventzilla_get_event, eventzilla_list_event_transactions and 8 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.27.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 1Claude Code: deny
  • eventzilla_toggle_event_salesWRITE: publish (status true) or unpublish (status false) ticket sales of one event.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_toggle_event_sales" says "toggle": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: publish (status true) or unpublish (status false) ticket sales of one event. Unpublishing stops attendees from buying tickets on the event page; publishing starts public sales again. Existing orders are not touched and no money moves through this tool. Idempotent. POST /events/togglesales.

    Annotations the server declares

    • title: Turn ticket sales on or off
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 10Show 10 read-only tools
  • eventzilla_get_attendeeOne attendee by id: name, ticket type, barcode, check-in status, order reference, registration answers.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_get_attendee" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One attendee by id: name, ticket type, barcode, check-in status, order reference, registration answers. GET /attendees/{attendeeid}.

    Annotations the server declares

    • title: Get attendee
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_get_eventOne event by id: title, description, dates, time zone, venue, status, tickets sold/total, URL, categories.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_get_event" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One event by id: title, description, dates, time zone, venue, status, tickets sold/total, URL, categories. GET /events/{eventid}.

    Annotations the server declares

    • title: Get event
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_get_transactionOne transaction (order) by checkout id or order reference number: amount, ticket count, status, event date.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_get_transaction" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One transaction (order) by checkout id or order reference number: amount, ticket count, status, event date. Read-only. GET /transactions/{identifier}.

    Annotations the server declares

    • title: Get transaction
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_get_userOne organizer or sub-organizer by user id.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_get_user" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One organizer or sub-organizer by user id. GET /users/{userid}.

    Annotations the server declares

    • title: Get organizer
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_list_categoriesList the event categories (names to use as the category filter in eventzilla_list_events).Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_list_categories" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the event categories (names to use as the category filter in eventzilla_list_events). GET /categories.

    Annotations the server declares

    • title: List event categories
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_list_event_attendeesList the attendees (registrations) of one event: name, ticket type, barcode, check-in status, order reference and answers to registration questions.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_list_event_attendees" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    List the attendees (registrations) of one event: name, ticket type, barcode, check-in status, order reference and answers to registration questions. The API returns the whole list in one reply (no paging). GET /events/{eventid}/attendees.

    Annotations the server declares

    • title: List event attendees
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_list_event_transactionsList the orders (transactions) of one event: order reference, checkout id, date, amount, number of tickets and status.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_list_event_transactions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    List the orders (transactions) of one event: order reference, checkout id, date, amount, number of tickets and status. Read-only. GET /events/{eventid}/transactions.

    Annotations the server declares

    • title: List event transactions
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_list_eventsList the events in the Eventzilla account: id, title, dates and times, venue, status, tickets sold and total, categories and the public URL.Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_list_events" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    List the events in the Eventzilla account: id, title, dates and times, venue, status, tickets sold and total, categories and the public URL. Use the id (and dateid) in the other tools. Filter by status and category name. GET /events.

    Annotations the server declares

    • title: List events
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_list_ticket_typesList the ticket types of one event: id, title, price, quantity, sales window and limits, plus its donation ticket options (donation_options).Reads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_list_ticket_types" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "eventzilla_list_ticket_types" says "list" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    List the ticket types of one event: id, title, price, quantity, sales window and limits, plus its donation ticket options (donation_options). GET /events/{eventid}/tickets.

    Annotations the server declares

    • title: List ticket types
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • eventzilla_list_usersList the account's organizer and sub-organizer users: name, company, contact details, time zone, user type.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "eventzilla_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the account's organizer and sub-organizer users: name, company, contact details, time zone, user type. GET /users.

    Annotations the server declares

    • title: List organizers
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://eventzilla.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://eventzilla.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://eventzilla.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://eventzilla.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.27.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http eventzilla https://eventzilla.usefulapi.io/mcp
claude mcp add --transport http eventzilla https://eventzilla.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__eventzilla__eventzilla_list_events",
      "mcp__eventzilla__eventzilla_get_event",
      "mcp__eventzilla__eventzilla_list_event_transactions",
      "mcp__eventzilla__eventzilla_list_event_attendees",
      "mcp__eventzilla__eventzilla_list_ticket_types",
      "mcp__eventzilla__eventzilla_list_categories",
      "mcp__eventzilla__eventzilla_get_attendee",
      "mcp__eventzilla__eventzilla_get_transaction",
      "mcp__eventzilla__eventzilla_list_users",
      "mcp__eventzilla__eventzilla_get_user"
    ],
    "ask": [],
    "deny": [
      "mcp__eventzilla__eventzilla_toggle_event_sales"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as eventzilla. Review it before you use it.

Capability tags behind 11 rules
  • mcp__eventzilla__eventzilla_list_events untrusted-input
  • mcp__eventzilla__eventzilla_get_event untrusted-input
  • mcp__eventzilla__eventzilla_list_event_transactions untrusted-input
  • mcp__eventzilla__eventzilla_list_event_attendees untrusted-input
  • mcp__eventzilla__eventzilla_list_ticket_types untrusted-input
  • mcp__eventzilla__eventzilla_list_categories untrusted-input
  • mcp__eventzilla__eventzilla_get_attendee untrusted-input
  • mcp__eventzilla__eventzilla_get_transaction untrusted-input
  • mcp__eventzilla__eventzilla_list_users private-data, untrusted-input
  • mcp__eventzilla__eventzilla_get_user untrusted-input
  • mcp__eventzilla__eventzilla_toggle_event_sales untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/eventzilla/verify?hash=91544303b6c71e894b680e013330e67fe4b8d4ea8e87a8b9a9519a4c95502025" | jq -e '.changed == false'

Pinned hash 91544303b6c7, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/eventzilla/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/eventzilla
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/eventzilla.svg)](https://radar.anlyon.com/servers/io.usefulapi/eventzilla)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Eventzilla MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Eventzilla MCP by usefulapi safe?

No scan can promise that. What its definitions show: 11 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Eventzilla MCP by usefulapi delete data?

Yes. 1 tool can delete, cancel or revoke something: eventzilla_toggle_event_sales.

Can the Eventzilla MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Eventzilla MCP by usefulapi have?

11 tools: 1 destructive, 10 read. eventzilla_toggle_event_sales, eventzilla_list_events, eventzilla_get_event, eventzilla_list_event_transactions, eventzilla_list_event_attendees, eventzilla_list_ticket_types, eventzilla_list_categories, eventzilla_get_attendee and 3 more.

Does the Eventzilla MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Eventzilla MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Eventzilla MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.