Koskamo

EventCompletion MCP

An official MCP server that allows AI agents to search a curated catalogue of source-verified events, retrieve details like progress and dates, and create new unlisted event countdown pages. It supports tools for searching, listing upcoming events, getting specific event details, registering for API keys, and creating events.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

EventCompletion MCP logo, by EventCompletionVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by EventCompletion
You need:Key + confirmed contact e-mail10 events per day per key
MCP endpoint (Streamable HTTP)
https://eventcompletion.com/mcp
Vendor documentation

What you can do with it

  • Search for specific events by name or category
  • Check the current progress or start date of an event
  • Create a new unlisted event countdown page
  • List upcoming events starting soonest

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
eventcompletion 1.0.0
MCP protocol
2025-06-18
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

EventCompletion tracks the progress of events between a start and an end date and keeps a curated, source-verified catalogue (sports, festivals, trade shows, French school holidays, French political calendar…). Use search_events / upcoming_events / get_event to answer questions about dates; every event has a page_url worth citing. Dates are inclusive calendar days. To add an event, call register_agent once (keep the api_key, send it as "Authorization: Bearer <key>"), confirm the contact e-mail, then create_event.

Tools

5 advertised

search_events — Search events
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

search_events input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Default 10."
    },
    "query": {
      "type": "string",
      "description": "Words to look for, e.g. \"fiba world cup\" or \"vacances zone b\"."
    },
    "status": {
      "enum": [
        "ongoing",
        "upcoming",
        "completed",
        "all"
      ],
      "type": "string",
      "description": "Default: all."
    },
    "category": {
      "type": "string",
      "description": "e.g. sport, culture, trade-show, tech, school, politics, institutions, civic, music, market, tv-film."
    },
    "language": {
      "enum": [
        "fr",
        "en"
      ],
      "type": "string",
      "description": "Language of the event page."
    }
  }
}
search_events annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
upcoming_events — Upcoming events
Advertised by the server during the last successful anonymous check.
Advertised read-only

Events that start soonest (curated catalogue). Use it for "what is coming up?" questions.

upcoming_events input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "category": {
      "type": "string"
    },
    "language": {
      "enum": [
        "fr",
        "en"
      ],
      "type": "string"
    },
    "within_days": {
      "type": "integer",
      "maximum": 730,
      "minimum": 1,
      "description": "Only events starting within this many days. Default 90."
    }
  }
}
upcoming_events annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_event — Get an event
Advertised by the server during the last successful anonymous check.
Advertised read-only

Details of one event by slug (the last part of its URL), including progress right now and where its dates were verified.

get_event input schema
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "e.g. \"wimbledon-2027\"."
    }
  }
}
get_event annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
register_agent — Get an API key
Advertised by the server during the last successful anonymous check.

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.

register_agent input schema
{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 60,
      "minLength": 3,
      "description": "Name of your agent or client, e.g. \"Acme research assistant\"."
    },
    "contact_email": {
      "type": "string",
      "description": "Optional but required to create events. A human must confirm it."
    }
  }
}
register_agent annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
create_event — Create an event
Advertised by the server during the last successful anonymous check.

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.

create_event input schema
{
  "type": "object",
  "required": [
    "name",
    "start_date",
    "end_date"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 120,
      "minLength": 3
    },
    "end_date": {
      "type": "string",
      "description": "Last day (inclusive), YYYY-MM-DD, not before start_date."
    },
    "language": {
      "enum": [
        "fr",
        "en"
      ],
      "type": "string",
      "description": "Language of the page. Default en."
    },
    "start_date": {
      "type": "string",
      "description": "First day, YYYY-MM-DD."
    },
    "description": {
      "type": "string",
      "maxLength": 500
    }
  }
}
create_event annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
464 ms
95th percentile latency
464 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 464 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http eventcompletion-mcp https://eventcompletion.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add eventcompletion-mcp --url https://eventcompletion.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable eventcompletion-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "eventcompletion-mcp": {
      "url": "https://eventcompletion.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "eventcompletion-mcp": {
      "type": "streamableHttp",
      "url": "https://eventcompletion.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start eventcompletion-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "eventcompletion-mcp": {
      "type": "http",
      "url": "https://eventcompletion.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http eventcompletion-mcp https://eventcompletion.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "eventcompletion-mcp": {
      "url": "https://eventcompletion.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "eventcompletion-mcp": {
      "serverUrl": "https://eventcompletion.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like EventCompletion MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run EventCompletion MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing