Skip to main content
Glama
EternalEngineOS

ee-mcp-public

by EternalEngineOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ee-mcp-public

No user-submitted related servers found.

    Related Servers

    • coinmarketcap-keyless-mcp

      JackSmack1971
      A
      license
      B
      quality
      A
      maintenance
      Enables credential-free, read-only access to selected public market-data routes via 13 typed MCP tools covering asset mapping, metadata, quotes, listings, global metrics, Fear & Greed, Altcoin Season, and CMC index data.
      13
      MIT

    • Kiwify MCP Server

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Kiwify sales, subscriptions, products, and affiliates via the official API. Read-only access for viewing data.
      MIT

    • Meta Ads MCP Server

      isaganiesteron
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to Meta Ads API, enabling campaign management, creative analysis, targeting research, and performance analytics via 39 tools.
      -
    • Nostradamus Intellect by NostradamusIntellect

      Nostradamus Intellectofficial

      NostradamusIntellect
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to search, read, and verify sealed forecasts and public-record cards, inspect resolution calendars, engine strands, sensor alerts, and wire headlines, and check whether stories are independent events or echoes. All access is read-only and requires no key, account, or dependencies.
      159 npm
      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

    B3.1/5.0

    Scored across 43 tools

    Disambiguation2/5

    Several tools have near-identical names and purposes, such as getApiKeys/listApiKeys, getProviders/listProviders, and getWebhooks/listWebhookEvents, which only differ by internal API module. With 43 tools, an agent can easily select the wrong variant despite reading descriptions.

    Naming Consistency3/5

    The set is consistently camelCase with get/list prefixes, but it mixes getX and listX for collection endpoints and creates duplicate-looking names across the email and payment domains. The pattern is readable but not predictable enough to be considered mostly consistent.

    Tool Count2/5

    43 tools is well above a comfortable MCP surface and many are near-duplicates (getApiKeys/listApiKeys, getProviders/listProviders). The server covers two domains, but the number feels heavy rather than tightly scoped.

    Completeness3/5

    As a read-only/public surface, it exposes a broad set of list and detail endpoints across email and payment resources. However, several resources are list-only with no detail lookup, and there are no write or management operations, so lifecycle coverage is incomplete for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources