Skip to main content
Glama
paracetamol951

P-Link-MCP

by paracetamol951
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to P-Link-MCP

No user-submitted related servers found.

    Related Servers

    • remit.md MCP Server

      pay-skill
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.
      3 npm
      MIT
    • paean-pay-mcp by paean-ai

      paean-pay-mcpofficial

      paean-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to send and receive USDC stablecoin payments on Base and Solana blockchains through MCP tools for wallet operations, balance checks, payment requests, and transfers.
      11 npm
      7
      MIT

    • Fin-MCP Payment Server

      Veri5ied
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with multiple payment providers (Stripe, Paystack) through a unified API. Supports payment initialization, verification, refunds, customer management, and invoicing without requiring knowledge of specific provider implementations.
      2
      -

    • Magpie MCP Server

      domdanao
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Magpie Payment Platform APIs for processing payments, creating checkout sessions, sending invoices, and managing payment links through natural conversation.
      73 npm
      2
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as funding, transaction retrieval, wallet management, and payments. However, get_wallet_and_otp combines wallet creation and OTP retrieval, which could cause confusion with login_with_otp, leading to minor ambiguity in their overlapping OTP-related functions.

    Naming Consistency3/5

    The naming is mixed with some consistency in verb_noun patterns like get_transaction_state and get_wallet_history, but deviations exist such as fund_my_wallet (verb_pronoun_noun), pay_and_get_402_protected_url (complex compound), and ping (single word). This creates a readable but inconsistent convention overall.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a P-Link wallet and payment management server. Each tool serves a clear function in handling wallets, transactions, payments, and server health, making the set comprehensive without being overwhelming.

    Completeness4/5

    The tool set covers key operations like wallet creation, funding, transaction history, payments, and authentication, supporting core workflows. A minor gap is the lack of tools for updating wallet details or managing tokens beyond basic retrieval, but agents can work around this with the existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources