Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Ethora MCP Server

No user-submitted related servers found.

    Related Servers

    • Coolify MCP Server

      StuMason
      F
      license
      A
      quality
      F
      maintenance
      Enables interaction with Coolify applications and resources through the Coolify API via a standardized interface, supporting application management operations such as listing, starting, stopping, restarting, and deploying.
      11
      13
      -

    • aurorarepos-mcp

      KotDath
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search Aurora OS app store, inspect app and release information, and manage developer applications including RPM upload, metadata editing, and publication scheduling.
      17
      MIT
    • Hellō Admin MCP Server by hellocoop

      Hellō Admin MCP Serverofficial

      hellocoop
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to create and manage Hellō applications with full developer context, supporting app creation, updates, secret generation, and logo management through a single unified tool.
      1
      49 npm
      4
      MIT

    • MCP REST Server

      gyuco
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with any REST API through token or login authentication, with automatic Swagger/OpenAPI documentation integration for endpoint discovery and comprehensive HTTP request support.
      7
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 89 tools

    Disambiguation2/5

    The tool descriptions are detailed, but the set is full of near-duplicate variants distinguished only by auth mode, legacy vs v2, or async vs wait behavior (e.g. ethora-sources-docs-upload vs ethora-sources-docs-upload-v2, ethora-sources-site-crawl-v2 vs ethora-sources-site-crawl-v2-wait, legacy bot tools vs agents tools). An agent would frequently struggle to pick the right variant, especially under time pressure.

    Naming Consistency3/5

    Names are readable and consistently ethora-prefixed, but conventions are mixed: noun-verb and verb-noun orders both appear, singular/plural varies (user vs users, agent vs agents), and wait/v2 suffixes are placed inconsistently (ethora-wait-broadcast-job-v2 vs ethora-sources-site-crawl-v2-wait). The pattern is recognizable, but far from uniform.

    Tool Count1/5

    With 89 tools, this far exceeds the 50+ extreme threshold in the calibration guide. Many tools are variants or wrappers of the same underlying operation, which inflates the surface and creates major selection overhead for agents.

    Completeness3/5

    The server covers a broad set of domains—apps, chats, messages, RAG sources, agents, files, users, tokens, and wallets—but lifecycle coverage is uneven. Apps and agents lack delete operations, users only have register/batch-create/login, and wallet support is a single balance-read, leaving notable gaps for full CRUD workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources