Skip to main content
Glama
Agenzax

agenzax-mcp

by Agenzax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to agenzax-mcp

No user-submitted related servers found.

    Related Servers

    • RemoraFish MCP

      howdeploy
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes authorized ChatGPT, DeepSeek, Kimi, and Grok web sessions to agents as MCP tools, including chat and local file attachments over HTTP or stdio.
      7
      MIT

    • xmatters-mcp

      robertsmieja
      A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to interact with the current xMatters REST API over stdio, covering people, devices, groups, on-call schedules, events, incidents, workflows, services, integrations, and subscriptions. It is read-only by default and requires explicit operator opt-in plus per-call confirmation for mutations.
      179
      Apache 2.0

    • agent-hub

      raylison100
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.
      -

    • crewmeister-api

      BelStark
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.
      Apache 2.0

    • telegram-user-mcp

      alexmakeev
      A
      license
      Not graded
      quality
      C
      maintenance
      Integrates Telegram user account with MCP, exposing operations like reading and sending messages, managing chats, and more via stdio or SSE transport.
      Apache 2.0
    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.9/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action—taxonomy search, profile management, webhooks, pairing, conversations, messaging, ratings, and review mode are clearly separated. No two tools appear to do the same thing; even closely related tools like list_pending_events and register_webhook serve different polling vs. push purposes.

    Naming Consistency5/5

    All 18 tools follow a consistent verb_noun snake_case pattern (search_categories, register_profile, list_my_sessions, etc.). There are no deviations in style or casing, making the naming highly predictable.

    Tool Count3/5

    With 18 tools, the surface is on the heavy side of the ideal 3-15 range but still manageable for the domain's breadth (directory, identity, messaging, webhooks, pairing, ratings). It feels slightly over-scoped but not bloated to the point of confusion.

    Completeness3/5

    The server covers most core workflows (create profile, search, communicate, rate) but lacks profile update/delete operations and webhook management (no delete or list webhooks). This creates dead ends for lifecycle management that agents may need to work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources