Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PnL Labs — Solana Trust & Risk Checks

REMOTE · API.PNLLABS.COM · SCANNED SEP 20

Trust checks for Solana trading: realized-PnL wallet trust, token safety, trade cost, forensics.

Available components

0 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 551 tokens (~137/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the PnL Labs — Solana Trust & Risk Checks MCP server?

PnL Labs — Solana Trust & Risk Checks is a hosted endpoint at https://api.pnllabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.pnllabs.com

# add to Claude Code
claude mcp add --transport http pnllabs-pnllabs 'https://api.pnllabs.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "pnllabs-pnllabs": {
      "url": "https://api.pnllabs.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pnllabs-pnllabs": {
      "type": "http",
      "url": "https://api.pnllabs.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.pnllabs-pnllabs]
url = "https://api.pnllabs.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pnllabs-pnllabs": {
      "type": "remote",
      "url": "https://api.pnllabs.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pnllabs-pnllabs --url 'https://api.pnllabs.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pnllabs-pnllabs:
    url: "https://api.pnllabs.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pnllabs-pnllabs": {
      "Transport": "http",
      "Url": "https://api.pnllabs.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add pnllabs-pnllabs -t streamable-http -u 'https://api.pnllabs.com/mcp'
// mcp.json
{
  "mcpServers": {
    "pnllabs-pnllabs": {
      "type": "http",
      "url": "https://api.pnllabs.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 30 Aug 26 +1
    • Stability: 0.97 → pass security
  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Aug 26 0
    • Authorization: unverified → partial security
    • Tool “check_token_safety” rewrote its description, which is the text the model reads security
    • Tool “check_trade_cost” rewrote its description, which is the text the model reads security
    • Tool “check_wallet_forensics” rewrote its description, which is the text the model reads security
    • Tool “check_wallet_trust” rewrote its description, which is the text the model reads security
    • “check_token_safety” reworded the description of “mint” cosmetic
    • “check_trade_cost” reworded the description of “size_sol” cosmetic
    • “check_wallet_forensics” reworded the description of “address” cosmetic
    • “check_wallet_trust” reworded the description of “address” cosmetic
    • Tool “check_token_safety” changed its title: Check Token Structural Risk cosmetic
    • Tool “check_trade_cost” changed its title: Estimate Trade Execution Cost cosmetic
    • Tool “check_wallet_forensics” changed its title: Trace Wallet Funding Origin cosmetic
    • Tool “check_wallet_trust” changed its title: Check Wallet Trust cosmetic
  • 1 Aug 26 0
    • Schema quality: unverified → excellent functional
    • Stability: unverified → 0.03 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://api.pnllabs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.pnllabs.com CN=YE2,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 51bb5dee5374ba0bc78025d40e13a39468b
SANs: api.pnllabs.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.pnllabs.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pnllabs.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.pnllabs.com/mcp Verified 200
http (plaintext) http://api.pnllabs.com/mcp HTTPS enforced 308 https://api.pnllabs.com/mcp
MCP tools · 4 exposed · ~473 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_token_safety ~133

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.

NameTypeReqDescription
mintstringyesSolana token mint address (base58, 32-44 chars)

No output schema declared.

No examples provided.

check_trade_cost ~119

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).

NameTypeReqDescription
mintstringyesSolana token mint address (base58)
size_solnumberTrade size in SOL (default 0.5)

No output schema declared.

No examples provided.

check_wallet_forensics ~92

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.

NameTypeReqDescription
addressstringyesSolana wallet address (base58, 32-44 chars)

No output schema declared.

No examples provided.

check_wallet_trust ~129

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.

NameTypeReqDescription
addressstringyesSolana wallet address (base58, 32-44 chars)

No output schema declared.

No examples provided.

Common questions

What is the PnL Labs — Solana Trust & Risk Checks MCP server?

PnL Labs — Solana Trust & Risk Checks is an MCP server listed in the public MCP registry as io.github.PnLlabs/pnllabs. Trust checks for Solana trading: realized-PnL wallet trust, token safety, trade cost, forensics. This page covers its hosted endpoint (https://api.pnllabs.com/mcp).

Is the PnL Labs — Solana Trust & Risk Checks MCP server safe to use?

PnL Labs — Solana Trust & Risk Checks scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PnL Labs — Solana Trust & Risk Checks MCP server expose?

PnL Labs — Solana Trust & Risk Checks exposes 4 tools: check_wallet_trust, check_wallet_forensics, check_trade_cost, check_token_safety. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.

Does the PnL Labs — Solana Trust & Risk Checks MCP server require authentication?

No. We connected to PnL Labs — Solana Trust & Risk Checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PnL Labs — Solana Trust & Risk Checks MCP server still maintained?

PnL Labs — Solana Trust & Risk Checks is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.