com.eventassets/eventassets
EventAssets
Is the EventAssets MCP server down? No. It is up and needs auth (HTTP 403), probed 2026-11-09.
Plan and host your events: event page, guest list, RSVP, seating, agenda, budget and media.
needs auth probed 2026-11-14 · unchanged since 2026-11-09 · HTTP 403
Streamable HTTP error: Error POSTing to endpoint: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content
- Endpoint
- https://api.eventassets.com/mcp (streamable-http)
- Host
- api.eventassets.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.eventassets.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.eventassets.com, PKCE S256, grants authorization_code, refresh_token.
Scopes events:read events:write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://eventassets.com
- Registry
- active, updated 2026-11-08 · registry entry
Compare this server with others.
More servers
Servers that mention seating or agenda.
- Contio MeetingOS ai.contio/meetingos · needs auth
- LivingMeta — AI in Research ai.livingmeta/ai-in-research · needs auth
- app.agendaforge/agendaforge · alive
- app.agendaforge/docs · alive
- app.seatcanvas/seatcanvas · alive
- brussels.toots/tickets · alive
- Alfabot MCP Server cl.alfabot/mcp-server · alive
- OpenAgenda com.openagenda/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 403 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.