Remote MCP server for searching EventCompletion's curated, source-verified event catalogue and creating unlisted public progress pages for events.
What you can do
Search the curated catalogue by words in an event name or description, with optional status, category and language filters
List the soonest upcoming events for "what's coming up?" questions
Fetch one event's details by slug, including current progress and where its dates were verified
Register an agent to obtain an API key and confirm a contact e-mail
Create an unlisted public progress page for an event, with inclusive calendar-day dates
When to use it
Useful when an assistant needs to answer date questions about sports, festivals, trade shows, school holidays or political calendars from a source-verified catalogue, or when you want to publish a shareable progress page for an event you are tracking.
Requirements
A remote streamable HTTP endpoint at eventcompletion.com; no local package or runtime. No authentication is needed for searching. Creating events requires an API key from register_agent, sent as an Authorization Bearer header, plus a confirmed contact e-mail.
Before you install
register_agent issues an API key that is shown only once and should be kept secret; it is sent as an Authorization Bearer header. A contact e-mail is required to create events and receives a confirmation link. create_event publishes a page reachable by its URL (unlisted, not in the catalogue or sitemap) and is limited to 10 per day.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.eventcompletion%2Fevents/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Search EventCompletion's curated events by words in the name or description (every word must match, any order), optionally filtered by status, category and language. Returns dates, progress, location and the page URL.
Parameterslimitquerystatuscategorylanguage
upcoming_events
Upcoming events
Events that start soonest (curated catalogue). Use it for "what is coming up?" questions.
Parameterslimitcategorylanguagewithin_days
get_event
Get an event
Details of one event by slug (the last part of its URL), including progress right now and where its dates were verified.
Parametersslugrequired
register_agent
Get an API key
Issue an API key for your agent (shown once, keep it). Send it as "Authorization: Bearer <key>" on later requests for higher rate limits. Give a contact_email to be able to create events: a confirmation link is sent to it.
Parametersnamerequiredcontact_email
create_event
Create an event
Create a public progress page for an event (needs an API key whose contact e-mail is confirmed; max 10 per day). The event is unlisted: it is reachable by its URL but not featured in the catalogue or sitemap. Dates are inclusive calendar days.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.