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.

Haris Guardian - Solana Token Risk Check

REMOTE · HARIS-API.VERCEL.APP

Read-only Solana SPL/Token-2022 rug-risk check: 0-100 score (higher=riskier) with reasons.

63 Trust /100

Last scanned (2 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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 Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 476 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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
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.

  • 5 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 62

    First indexed and scored.

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 5 Nov 2026 · Probed https://haris-api.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of haris-api.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://haris-api.vercel.app/mcp Verified 200
http (plaintext) http://haris-api.vercel.app/mcp HTTPS enforced 308 https://haris-api.vercel.app/mcp
MCP tools · 4 exposed · ~383 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
batch_check_solana_tokens ~67

Batch Solana token risk check (PAID, x402 over REST): up to 20 mints in one call for one flat price. This tool returns exact x402 payment instructions for POST /v1/paid/batch-check.

NameTypeReqDescription
mintsarrayyes–

No output schema declared.

No examples provided.

check_solana_token ~107

Scam/rug risk check for a Solana SPL or Token-2022 token mint. Returns a 0-100 risk score (HIGHER = RISKIER), a verdict, and flags with plain-English reasons: mint/freeze authority, permanent delegate, transfer hooks/fees, holder concentration, liquidity, LP burn/lock %, Streamflow locks and a simulated buy+sell (honeypot test). Read-only; never signs or trades.

NameTypeReqDescription
mintstringyes–

No output schema declared.

No examples provided.

deep_check_solana_token ~106

Deep Solana token risk check (PAID, x402 over REST): holder concentration (top1/top5/top10 % of supply), top wallets linked by a shared funder (bundles/insiders), creator-funded holders, fresh wallets, LP lock/burn status, authorities, score + reasons. This tool returns exact x402 payment instructions for POST /v1/paid/deep-check; pay with any x402 client.

NameTypeReqDescription
mintstringyes–

No output schema declared.

No examples provided.

diff_solana_token ~103

Watch/diff a Solana token: pass the mint and a previous Haris result (from check_solana_token or an earlier diff); returns alerts on what changed (authority re-enabled, LP unlocked, liquidity pulled, sell blocked, new red flags) plus the fresh result. Shares the free tier with check_solana_token; then x402 via POST /v1/paid/diff.

NameTypeReqDescription
mintstringyes–
previousobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the Haris Guardian - Solana Token Risk Check MCP server?

Haris Guardian - Solana Token Risk Check is a hosted endpoint at https://haris-api.vercel.app/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 · haris-api.vercel.app

# add to Claude Code
claude mcp add --transport http fitness9991-haris-guardian 'https://haris-api.vercel.app/mcp'
Common questions

What is the Haris Guardian - Solana Token Risk Check MCP server?

Haris Guardian - Solana Token Risk Check is an MCP server listed in the public MCP registry as io.github.fitness9991/haris-guardian. Read-only Solana SPL/Token-2022 rug-risk check: 0-100 score (higher=riskier) with reasons. This page covers its hosted endpoint (https://haris-api.vercel.app/mcp).

Is the Haris Guardian - Solana Token Risk Check MCP server safe to use?

Haris Guardian - Solana Token Risk Check scores 63 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 Haris Guardian - Solana Token Risk Check MCP server expose?

Haris Guardian - Solana Token Risk Check exposes 4 tools: check_solana_token, deep_check_solana_token, batch_check_solana_tokens, diff_solana_token. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.

Does the Haris Guardian - Solana Token Risk Check MCP server require authentication?

No. We connected to Haris Guardian - Solana Token Risk Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Haris Guardian - Solana Token Risk Check MCP server still maintained?

Haris Guardian - Solana Token Risk Check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.