Skip to main content
Glama
MyOpenFund

MyOpenFund MCP Server

Official
by MyOpenFund

Related Servers

Alternatives to MyOpenFund MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes two tools, ask and search, over both streamable HTTP and stdio transports, letting MCP clients pull grounded, inline-cited answers or ranked chunks from an indexed corpus of registered repositories and web pages. The HTTP endpoint is unauthenticated and pinned to the public visibility tier, while the stdio proxy carries the caller's API key and therefore their tier.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search, record, correct, and review the provenance and version history of memories, and to obtain answers composed from guarded context in which private values are replaced by placeholders and resolved locally on the device. Exposes these capabilities through dependency-free tools over stdio.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A thin stdio gateway to Nodus's Streamable HTTP MCP server, exposing a curated allowlist of tools for the Research Workbench. It enables secure, bearer-authenticated interactions with Nodus without graph logic or caching.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code and Cursor to search a documentation corpus, read specific pages, and locally ask grounded questions with verified citations over stdio or Streamable HTTP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Cursor and Claude Desktop to query a GRC platform over stdio or HTTP, with read-only access by default and opt-in create, update, and delete tools subject to platform authorization.
      3
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusing it with another. Its purpose—returning deployment metadata—is clear.

    Naming Consistency5/5

    With a single tool, there is no pattern to violate. The name `server_info` is clear snake_case and readable.

    Tool Count2/5

    A one-tool surface is very thin for a server whose name suggests fund/vault operations. The sole tool only reports deployment metadata rather than exposing domain functionality.

    Completeness1/5

    The surface is severely incomplete for a fund-oriented MCP server: it offers no tools to read or manage vault/fund data. `server_info` is introspection only and leaves obvious domain operations missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues