P-Link-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIKEY | Yes | Your P-Link API key (required). Get it from https://p-link.io/ApiDoc/Send |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wallet_and_otpC | Create a wallet for your email or get otp by email |
| login_with_otpC | Login using otp. Connect to your P-Link wallet using the one time password you received by email |
| fund_my_walletC | Fund wallet : Obtain a link in order to fund your wallet of the desired amount using a credit card, or the Solana address of your wallet if you want to fund your account using Solana. |
| get_private_key_of_walletC | Get the private key of your wallet on secured app https://p-link.io |
| send_moneyA | Send money to an email, Solana wallet or phone number. The provided email or phone can be used to claim the money of the wallet. If new user does not claim for 3 days, the money is returned to the sender. |
| request_payment_linkC | Create a payment link in order to request a payment to your account. This payment link can be used to pay you. Payment can be made using a credit card, or any Solana token (automatically converted to USDC) |
| get_wallet_infoC | Retrieve the wallet infos about the connected P-Link account (Solana wallet address, wallet balance, tokens detail) |
| get_transaction_stateC | Retrieve the state and details of a transaction using Solana trx ID |
| get_wallet_historyC | Transaction history : Retrieve list of the transactions related to the specified Solana wallet address (received and sent funds with dates) |
| pay_and_get_402_protected_urlC | Pay a HTTP 402 protected URL using your P-Link managed account, and returns the result |
| pingA | Simple MCP server health check. Returns { result: 'OK' } if the server is alive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.