Skip to main content
Glama
Sign In
Bridge MCP Server

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
      C
      quality
      B
      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.
      93
      447 npm
      9
      MIT

    • Yolfi MCP Server

      LanOgawa53420
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin crypto checkout, payment links, payment status checks, webhook verification, and webhook-based access logic into applications.
      MIT

    • Yolfi MCP server

      sSato8458
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications. It provides tools for registering workspaces, configuring settlement wallets and webhooks, creating paylinks, and verifying crypto payment status.
      MIT

    • Yolfi MCP Server

      emre08189
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic to applications. It also provides tools for workspace registration, settlement and webhook configuration, paylink creation, and crypto payment status checks.
      -
    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources