Skip to main content
Glama
dragonkhoi

Ramp MCP

by dragonkhoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Ramp MCP

No user-submitted related servers found.

    Related Servers

    • Mercury MCP

      dragonkhoi
      A
      license
      Not graded
      quality
      D
      maintenance
      Simple MCP server that interfaces with the Mercury API, allowing you to talk to your Mercury banking data from any MCP client like Cursor or Claude Desktop.
      4
      MIT

    • Copilot Money MCP

      ignaciohermosillacornejo
      A
      license
      A
      quality
      A
      maintenance
      This MCP server bridges Copilot Money with AI platforms like Claude and Cursor. It provides tools for fetching transactions, account balances, and automated data cleanup. By enabling secure, programmable access to financial records, it allows agents to perform complex tasks like transaction tagging and spending audits autonomously.
      14
      90 npm
      79
      MIT

    • razorpay-mcp

      indiamcp
      A
      license
      B
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that connects AI assistants like Claude directly to your Razorpay account.
      14
      23 npm
      1
      MIT

    • clawvault

      andrewszk
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for ClawVault - an AI agent payment security layer that enables Claude to request payments, check limits, and manage transactions with configurable rules.
      74 npm
      MIT

    • GOAT MCP Server

      cryptoleek-team
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude for Desktop with blockchain functionality, allowing users to check balances and send tokens on EVM and Solana chains through natural language interactions.
      -
    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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves credit card transactions, while the other retrieves statements with filtering capabilities. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool based on the need.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (get_credit_card_transactions and get_ramp_statements), using the same verb 'get' and snake_case formatting. This predictability aids in tool identification and usage.

    Tool Count2/5

    With only two tools, the server feels under-scoped for a financial management domain like Ramp, which typically involves more operations such as creating transactions, updating details, or managing accounts. The limited set may hinder comprehensive agent workflows.

    Completeness2/5

    The tool surface is severely incomplete for a Ramp integration, covering only retrieval of transactions and statements. Missing are essential CRUD operations (e.g., create, update, delete), account management, or other financial actions, leading to significant gaps that will cause agent failures in broader tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources