Eventzilla MCP by usefulapi
REMOTE · EVENTZILLA.USEFULAPI.IO
Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1017 tokens (~92/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://eventzilla.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of eventzilla.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://eventzilla.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://eventzilla.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://eventzilla.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://eventzilla.usefulapi.io/mcp |
| Authorisation server | https://eventzilla.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eventzilla.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/eventzilla/ |
| http (plaintext) | http://eventzilla.usefulapi.io/mcp | Inconclusive | 302 | http://eventzilla.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
eventzilla_get_attendee Get attendee ~65
One attendee by id: name, ticket type, barcode, check-in status, order reference, registration answers. GET /attendees/{attendeeid}.
| Name | Type | Req | Description |
|---|---|---|---|
| attendee_id | integer | yes | Eventzilla attendee id (the id field in eventzilla_list_event_attendees). |
No output schema declared.
No examples provided.
eventzilla_get_event Get event ~56
One event by id: title, description, dates, time zone, venue, status, tickets sold/total, URL, categories. GET /events/{eventid}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Eventzilla event id. |
No output schema declared.
No examples provided.
eventzilla_get_transaction Get transaction ~55
One transaction (order) by checkout id or order reference number: amount, ticket count, status, event date. Read-only. GET /transactions/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Checkout id or order reference number. |
No output schema declared.
No examples provided.
eventzilla_get_user Get organizer ~38
One organizer or sub-organizer by user id. GET /users/{userid}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | Eventzilla user id. |
No output schema declared.
No examples provided.
eventzilla_list_categories List event categories ~32
List the event categories (names to use as the category filter in eventzilla_list_events). GET /categories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
eventzilla_list_event_attendees List event attendees ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Eventzilla event id. |
No output schema declared.
No examples provided.
eventzilla_list_event_transactions List event transactions ~102
List the orders (transactions) of one event: order reference, checkout id, date, amount, number of tickets and status. Read-only. GET /events/{eventid}/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Eventzilla event id. |
| limit | integer | – | Records per page, 1-100 (default 20). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
eventzilla_list_events List events ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only events in this category name (see eventzilla_list_categories). |
| limit | integer | – | Records per page, 1-100 (default 20). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
| status | string | – | Only events with this status. |
No output schema declared.
No examples provided.
eventzilla_list_ticket_types List ticket types ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Eventzilla event id. |
No output schema declared.
No examples provided.
eventzilla_list_users List organizers ~79
List the account's organizer and sub-organizer users: name, company, contact details, time zone, user type. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 20). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
eventzilla_toggle_event_sales Turn ticket sales on or off ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | Eventzilla event id. |
| status | boolean | yes | true = publish/open sales, false = unpublish/close sales. |
No output schema declared.
No examples provided.
How do I install the Eventzilla MCP by usefulapi server?
Eventzilla MCP by usefulapi is a hosted endpoint at https://eventzilla.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · eventzilla.usefulapi.io
claude mcp add --transport http io-usefulapi-eventzilla 'https://eventzilla.usefulapi.io/mcp'
What is the Eventzilla MCP by usefulapi server?
Eventzilla MCP by usefulapi is listed in the public MCP registry as io.usefulapi/eventzilla. Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales. This page covers its hosted endpoint (https://eventzilla.usefulapi.io/mcp).
Is the Eventzilla MCP by usefulapi server safe to use?
Eventzilla MCP by usefulapi scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Eventzilla MCP by usefulapi server expose?
Eventzilla MCP by usefulapi exposes 11 tools: eventzilla_list_events, eventzilla_get_event, eventzilla_list_event_transactions, eventzilla_list_event_attendees, eventzilla_list_ticket_types, and 6 more. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.
Does the Eventzilla MCP by usefulapi server require authentication?
Yes. Eventzilla MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Eventzilla MCP by usefulapi server still maintained?
Eventzilla MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.