Skip to main content
Glama
bakhtiersizhaev

openevidence-mcp

by bakhtiersizhaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to openevidence-mcp

No user-submitted related servers found.

    Related Servers

    • cdp-bridge

      Unagi-cq
      A
      license
      A
      quality
      B
      maintenance
      Connects MCP clients to real browser sessions via a Chromium plugin, enabling LLMs to read, scan, automate, and navigate web pages using the user's existing browser state.
      10
      174 PyPI
      304
      MIT

    • Medium Reader MCP

      wkbaran
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients like Claude to access a user's Medium account, including Following and For you feeds, full member-only posts, search, reading lists, and managing follows, saves, and claps after a one-time browser login.
      14
      47 npm
      MIT
    • Corvus MCP by ParendumOU

      Corvus MCPofficial

      ParendumOU
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP clients to an AI browser so agents can open and read pages, click, type, fill forms, take screenshots, and search within the user's logged-in browser session. Sensitive actions such as checkouts or payments require explicit approval.
      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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: authentication check, listing history, fetching an article, waiting for completion, and asking a question. No two tools overlap in functionality.

    Naming Consistency4/5

    All tools share an 'oe_' prefix and use underscores, but the naming pattern varies slightly: some are noun_verb (article_get, article_wait), others are noun_noun (auth_status, history_list), and one is a simple verb (ask). Mostly consistent with a minor deviation.

    Tool Count5/5

    With 5 tools covering authentication, history, retrieval, waiting, and question creation, the count is well-scoped for the server's purpose. Neither too few nor too many.

    Completeness4/5

    The tool set covers the core workflow: authentication, history listing, article retrieval, waiting for completion, and creating questions. Missing tools for updating or deleting articles, but those are likely unnecessary for the read-and-create domain.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources