Skip to main content
Glama
getpara

Para Wallet MCP Server

by getpara
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Para Wallet MCP Server

No user-submitted related servers found.

    Related Servers

    • AgentWallet MCP Server

      hifriendbot
      A
      license
      A
      quality
      D
      maintenance
      Provides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.
      29
      217 npm
      3
      MIT

    • BotWallet MCP Server

      botwallet-co
      A
      license
      A
      quality
      D
      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
      286 npm
      3
      Apache 2.0

    • ows-mcp-wallet

      Danmwihoti
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check balances and send transactions across multiple blockchains with automatic spending limit protection and policy enforcement.
      3
      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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: create_wallet for creation, get_wallet for single retrieval, list_wallets for batch retrieval, sign_raw for signing, and wait_for_wallet_ready for polling. The descriptions explicitly differentiate their functions, eliminating any ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: create_wallet, get_wallet, list_wallets, sign_raw, and wait_for_wallet_ready. This uniformity makes the set predictable and easy to understand at a glance.

    Tool Count5/5

    With 5 tools, this server is well-scoped for wallet management and signing operations. Each tool serves a clear, essential function without redundancy, fitting the typical range of 3-15 tools for a focused domain like MPC wallets.

    Completeness4/5

    The tool set covers core MPC wallet workflows: creation, retrieval (single and batch), signing, and status polling. A minor gap is the lack of update or delete operations for wallets, which might be intentional given the domain but could limit agent flexibility in some scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources