Skip to main content
Glama
bkawk

Ryft MCP

by bkawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Ryft MCP

No user-submitted related servers found.

    Related Servers

    • MCP Stripe Server

      atharvagupta2003
      A
      license
      Not graded
      quality
      F
      maintenance
      A server that integrates with Stripe for handling payments, customers, and refunds through the Model Context Protocol, providing a secure API to manage financial transactions.
      44
      MIT

    • stela-mcp

      Sachin-Bhat
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.
      14
      1
      Apache 2.0
    • Paddle MCP Server by PaddleHQ

      Paddle MCP Serverofficial

      PaddleHQ
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools for interacting with the Paddle Billing API, enabling users to manage products, prices, customers, transactions, subscriptions, and create custom financial reports.
      63
      394 npm
      51
      Apache 2.0
    • stripe by stripe

      stripeofficial

      stripe
      A
      license
      Not graded
      quality
      C
      maintenance
      The Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.
      16,994 npm
      1,851
      -

    • Tradovate MCP Server

      alexanimal
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with the Tradovate API for managing trading contracts, positions, orders, and accounts.
      1
      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

    C2.8/5.0

    Scored across 69 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (accounts, customers, disputes, etc.) with specific CRUD operations, making it easy to distinguish between them. The naming convention clearly indicates both the resource and action, preventing misselection.

    Naming Consistency5/5

    The naming follows a perfectly consistent pattern throughout: resource.action (e.g., accounts.create, customers.get, disputes.list). All tools use lowercase with dot notation separating resource and verb, creating a predictable and readable structure. There are no deviations in naming style.

    Tool Count2/5

    With 69 tools, the count is excessive for most agent workflows and feels heavy for the payment processing domain. While the domain is comprehensive, this many tools creates cognitive load and may overwhelm agents. A more focused subset would be more appropriate for typical use cases.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage across all major payment processing domains: accounts, customers, payments, disputes, subscriptions, transfers, and webhooks. Every resource type has create, get, update, and list operations where applicable, with no obvious gaps in functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources