Skip to main content
Glama
brian7989

benepass-mcp

by brian7989
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to benepass-mcp

No user-submitted related servers found.

    Related Servers

    • h1-mcp

      gabdevele
      A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to HackerOne Hacker API data including program policies, structured scopes, scope exclusions, hacktivity/prior art, and your own reports through MCP clients.
      8
      MIT

    • mcp-nightscout

      lozit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to a Nightscout instance for glucose readings, treatments, and deterministic server-side aggregates, allowing users to discuss their diabetes data with an AI assistant without write permissions.
      MIT

    • Bity

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only access to Bity cryptocurrency account balances, market data (ticker, order book, trades), and order history via the official API.
      MIT

    • Klaviyo MCP

      scalably-io
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Klaviyo marketing data, including campaigns, flows, segments, metrics, reports, and customer profiles, across multiple Klaviyo accounts.
      24
      27 npm
      MIT

    • Stripe

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only querying of payments and billing data via the full official REST API, covering customers, charges, payment intents, subscriptions, invoices, refunds, and more.
      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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct operation (auth, list, get) on distinct resources (user, workspaces, accounts, benefits, transactions, HSA, documents). No two tools appear to overlap in purpose, making selection unambiguous.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_*, get_*, start_login, complete_login). Minor deviations include auth_status (noun-like) and logout (single verb), but overall the convention is clear and predictable.

    Tool Count5/5

    13 tools is within the ideal 3-15 range and aligns well with the server's scope of accessing Benepass data. Each tool serves a clear purpose without redundancy, making the set well-proportioned.

    Completeness4/5

    The surface covers core read operations (auth, lists, details) with no obvious dead ends. Minor gaps include the lack of individual transaction detail fetch and potential reverse-engineering fragility of HSA investments, but the main workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources