mcp server
PnL Labs — Solana Trust & Risk Checks
Trust checks for Solana trading: realized-PnL wallet trust, token safety, trade cost, forensics.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-31.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_token_safety(mint)- Analyzes structural risk of a Solana token from on-chain data: real-holder concentration with bonding-curve and liquidity-pool accounts excluded, presence of known sniper-bot addresses among early buyers, and a simulated buy/sell round trip to detect honeypot behavior. Returns: verdict (LOW_RISK, ELEVATED, HIGH_RISK, CRITICAL, UNKNOWN), stable reason codes, and top-holder percentages. Scope is structural only; it does not detect risk that exists purely in trading behavior. Required: mint.
check_trade_cost(mint, size_sol)- Estimates what a trade of a given size would cost in a Solana token's main liquidity pool. Returns: expected slippage in percent, an estimated round-trip cost calibrated against measured live execution overhead, a recommended maximum size in SOL, pool liquidity, and a verdict (ACCEPTABLE_COST, ELEVATED_COST, HIGH_COST, UNTRADEABLE, NO_POOL, UNKNOWN). Required: mint.
check_wallet_forensics(address)- Traces where a Solana wallet's funding came from and how old it is, using on-chain transfer history. Returns: origin classification (CEX_FUNDED, WALLET_FUNDED, UNKNOWN_ORIGIN, UNVERIFIABLE_ORIGIN), the funding transaction, wallet age, and a fresh_wallet flag. Required: address.
check_wallet_trust(address)- Recomputes the realized SOL profit and loss of a Solana wallet from its on-chain transaction history and returns a trust verdict. Returns: verdict (TRUSTED, NEUTRAL, UNTRUSTED, INSUFFICIENT, UNVERIFIABLE), a confidence level, realized profit/loss in SOL, the number of coins analyzed, stable reason codes, and flags such as known_sniper_bot. Returns UNVERIFIABLE when the history cannot be reconstructed reliably rather than estimating. Required: address.
Last successful function declaration observed on . Source: https://api.pnllabs.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.pnllabs.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.pnllabs.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | api.pnllabs.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json