Skip to main content
Glama

Related Servers

Alternatives to b2match-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      B
      maintenance
      Enables interaction with the Swapcard event platform API, providing tools to manage events, people, sessions, exhibitors, documents, custom fields, meetings, webhooks, and analytics through natural language.
      32
      -
    • F
      license
      B
      quality
      D
      maintenance
      Enables interaction with the Wisembly API to fetch and manage event data, including event details, participants, organizers, and locations.
      2
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to browse curated city event feeds, retrieve full details for individual events, and list an organizer's public calendar without authentication. It returns only public event metadata, stripping attendee, guest, host, and manager data before responding.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to browse public event listings from explore pages and fetch full detail for a single event — titles, descriptions, times, locations, host display names, and aggregate RSVP counts — across eight supported city regions. Keyless and read-only, with no guest lists, contact info, or authentication required.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Crisp customer support, live chat, CRM, and helpdesk data, including conversations, contacts, knowledge base, campaigns, operators, visitors, and site settings, via the official REST API v1.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables discovery and querying of public OpenBind structure-affinity datasets, experimental binding events, benchmark results, and live Fragalysis targets and observations through read-only REST endpoints without requiring an API key.
      -

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action, and the descriptions do a good job distinguishing near-neighbors (e.g. list_participants vs get_participant vs my_participation, and list_opportunities' published ids vs my_participation's opportunity ids). Some overlap remains between the 'my_' cluster (my_schedule, my_availability, my_meetings) and the agenda/session tools, but boundaries are largely workable.

    Naming Consistency4/5

    The dominant pattern is a clean verb_noun convention (get_event, list_participants, get_session, find_meeting_slots). Deviations are the consistent 'my_' viewer-scoped group (my_participation, my_schedule, my_availability, my_meetings) plus a couple of noun-style names (auth_status, meeting_recommendations), which is readable but not a single uniform pattern.

    Tool Count4/5

    22 tools is on the heavier side but justified by a genuinely broad domain covering events, participants, organisations, opportunities, agenda, sessions, speakers, meetings, availability, conversations, and notifications. Almost every tool targets a distinct resource, so few feel redundant, though a couple could arguably be merged.

    Completeness3/5

    Coverage of read/list/get operations is thorough across resources, but the surface is lopsided: there is no send-message operation for the conversation tools, no meeting booking beyond find_meeting_slots, and no create/update actions anywhere, leaving common writing workflows as dead ends. For a read-mostly client this is largely workable but leaves notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues