Skip to main content
Glama
grip-foundation

Grip MCP

Official
by grip-foundation
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Local

Related Servers

Alternatives to Grip MCP

No user-submitted related servers found.

    Related Servers

    • veyra-mcp

      zapxlabs
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to make non-custodial USDC payments on Base through an MCP endpoint, with server-enforced per-payment and daily caps, human approval bands, and recipient allowlists.
      7
      29 npm
      MIT

    • ARCANUM plugin for PayBox

      bunnyyxtan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and manage contract-guarded USDC wallets on Base with enforceable per-payment, daily, and monthly caps, vendor allowlists, escalation thresholds, and freeze controls. It provides read-only policy checks plus unsigned transaction proposals for payments, funding, vendor management, wallet creation, and module deployment without holding keys or broadcasting.
      Apache 2.0

    • BotWallet MCP Server

      botwallet-co
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.
      36
      60 npm
      4
      Apache 2.0

    • PulseNetwork MCP

      GTCC777
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with a wallet and access to 900+ pay-per-call intelligence APIs across 74 verticals, with automatic USDC payments on Base and built-in spend guardrails.
      5
      40 npm
      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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: creating staged payments, listing payments, settling/rejecting, and checking wallet info. No overlap or ambiguity.

    Naming Consistency4/5

    All tools start with 'grip_' and most follow a verb_noun pattern (create_payment, list_payments, settle_payment). The exception is 'grip_wallet', which is a noun phrase, but the inconsistency is minor given the small set.

    Tool Count5/5

    Four tools is well-scoped for a payment/wallet MCP server. It covers staging, settling, listing, and wallet info without being too few or excessive.

    Completeness4/5

    The tool surface covers the core payment workflow: create, settle/reject, list, and wallet info. A potential minor gap is lack of explicit cancellation for staged payments, but the reject option in settle effectively handles that.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources