Skip to main content
Glama
lnflash

Bridge MCP Server

by lnflash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bridge MCP Server

No user-submitted related servers found.

    Related Servers

    • BlindPay MCP Server

      blindpaylabs
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with BlindPay's stablecoin payment infrastructure, allowing users to create receivers, process payouts and payins across multiple blockchains, manage virtual accounts and wallets, and configure payment operations through natural language.
      16 npm
      10
      MIT

    • PayBridgeNP MCP Server

      paybridgenp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.
      31 npm
      1
      MIT
    • @payre/mcp by Payre-IO

      @payre/mcpofficial

      Payre-IO
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Payre's Web3 payment gateway for generating crypto checkout invoices, monitoring settlements, managing payout destinations, and inspecting analytics.
      18
      -
    • Cresium MCP Server by Cresium

      Cresium MCP Serverofficial

      Cresium
      F
      license
      A
      quality
      C
      maintenance
      Enables AI tools to manage financial operations through the Cresium Partner API, including transactions, payments, invoices, and wallet balances. It supports secure workflows such as bank address lookups, transfer previews, and signature request management.
      12
      5
      -
    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.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (create/get/list per entity). There is no overlap between customers, wallets, virtual accounts, transfers, external accounts, webhooks, and exchange rates, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent bridge_verb_noun pattern. Verbs are limited to create, get, and list, and nouns are consistently singular for get/create and plural for list operations, except for exchange_rates which is naturally plural.

    Tool Count4/5

    With 18 tools, the server is slightly above the typical 3-15 range but each tool corresponds to a necessary operation across seven distinct resource types. The count is justified for a payment-focused API, though it feels a bit heavy.

    Completeness3/5

    Core create/get/list operations are covered for most resources, but update and delete actions are missing across the board. Notably, webhooks only have create and list, lacking get and delete. These gaps could hinder full lifecycle management for an agent.

    Resources