Skip to main content
Glama
Sign In
eventor-mcp

eventor-mcp

by bjorges
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to eventor-mcp

No user-submitted related servers found.

    Related Servers

    • eventor-mcp

      JustinStafford
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude to query events, entries, start lists, results, clubs, members and activities across Eventor Australia, Sweden, Norway and IOF, with optional publishing of start and result lists. Responses are converted from Eventor's XML to compact JSON and cached, with read-only mode available to hide write tools.
      MIT

    • openproject-mcp

      OliverRhyme
      A
      license
      A
      quality
      D
      maintenance
      Exposes the OpenProject REST API as MCP tools for project management, including creating and managing projects, work packages, relations, attachments, users, notifications, watchers, boards, and reference data.
      37
      59 npm
      MIT

    • profixio

      prfafa
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only access to public Swedish sports competition data, including federations, districts, schedules, results, standings, team searches, matches by date, and detailed match protocols. It provides these capabilities through MCP tools without requiring login, a browser, or credentials.
      9
      MIT

    • datakilder-mcp

      smlhus1
      A
      license
      B
      quality
      B
      maintenance
      MCP server providing typed tools for Norwegian public data sources, enabling natural language queries to official datasets like SSB, Brønnøysund, MET, Kartverket, Entur, and more, without requiring API keys.
      47
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target distinct resources (events, organisations, classes, imports), and the descriptions clarify scope. However, get_event_entries, get_competitors, and get_entry_changes all concern 'who is participating' and differ mainly by scope (event vs club vs timestamps), which could cause occasional misselection.

    Naming Consistency5/5

    All eight tools follow a clean snake_case verb_noun pattern using get_, list_, and import_ prefixes consistently. The convention is predictable and easy to reason about.

    Tool Count5/5

    Eight tools is well-scoped for an orienteering event data server, with a sensible split between read operations and two publish/import writes. Each tool clearly earns its place.

    Completeness4/5

    The surface covers the core lifecycle: listing events/organisations, reading classes, entries, competitors, and publishing start/result lists. Minor gaps exist, such as no single-event detail fetch and no update/delete of entries, but agents can work around these.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Resources