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.

Rugsight

REMOTE · RUGSIGHT.RUGSIGHT.WORKERS.DEV

Solana token rug-risk scores. Free basic score; full report pay-per-call via x402 (0.03 USDC).

68 Trust /100

Last scanned (7 hours ago)

Scores higher than 53% 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 Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 305 tokens (~152/item across 2 items; 2 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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
    • Tool “get_token_risk_report” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Server version: 1.6.0 → 1.8.0 functional
  • 4 Nov 26 0
    • Server version: 1.5.1 → 1.6.0 functional
  • 2 Nov 26 +1

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

  • 31 Oct 26 +1
    • Tool “get_token_risk_report” rewrote its description, which is the text the model reads security
    • Tool “get_token_risk_score” rewrote its description, which is the text the model reads security
    • Schema quality: 126 → 143 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.3.0 → 1.5.1 functional
    • Server version: 1.2.0 → 1.3.0 functional
    • Server version: 1.1.0 → 1.2.0 functional
  • 30 Oct 26 65

    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://rugsight.rugsight.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rugsight.workers.dev CN=YE1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA384 6f145fd57da5b8122ac86840107d28c3fdb
SANs: *.rugsight.workers.dev, rugsight.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 rugsight.rugsight.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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://rugsight.rugsight.workers.dev/mcp Verified 200
http (plaintext) http://rugsight.rugsight.workers.dev/mcp Inconclusive 405
MCP tools · 2 exposed · ~243 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
get_token_risk_report ~176

Rugsight full risk report for a Solana SPL / Token-2022 token: mint & freeze authority, Token-2022 extensions, top-20 holder breakdown (wallets vs pools/programs/burn), liquidity, main-pool LP burn/lock status (burnedPct, lockedPct, unlockAt), 24h volume, pool age, every risk flag explained, 0-100 score and A-F grade (or IC = issuer-controlled for allowlisted regulated assets such as USDC, PYUSD, cbBTC or xStocks). Costs 0.03 USDC on Solana per call, paid with x402: call without payment to receive the PaymentRequired object, then retry with _meta["x402/payment"].

NameTypeReqDescription
mintstringyesSolana token mint address (base58)
NameTypeReqDescription
authorityHoldersobject––
checkedAtstring––
confidencestringyes–
decimalsinteger––
disclaimerstring––
extensionsarray––
flagsarrayyes–
freezeAuthoritystring|null––
gradestringyesA-F from the score; IC = issuer-controlled (allowlisted regulated/issuer asset)
holdersobject––
issuerobject|null––
issuerControlledboolean––
marketobject––
mintstringyes–
mintAuthoritystring|null––
namestring|null––
scoreintegeryes–
supplyUinumber––
symbolstring|null––
technicalGradestring––
tokenProgramstring––
verdictstring––

No examples provided.

get_token_risk_score ~67

Free basic risk score for a Solana token: 0-100 score, A-F grade (or IC for allowlisted issuer-controlled assets), verdict and risk flag codes. Free, no payment needed.

NameTypeReqDescription
mintstringyesSolana token mint address (base58)
NameTypeReqDescription
checkedAtstring––
confidencestring––
flagsarray––
gradestringyes–
issuerobject|null––
issuerControlledboolean––
mintstringyes–
scoreintegeryes–
technicalGradestring––
verdictstring––

No examples provided.

Install

How do I install the Rugsight MCP server?

Rugsight is a hosted endpoint at https://rugsight.rugsight.workers.dev/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 · rugsight.rugsight.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-rugsight-rugsight-rugsight 'https://rugsight.rugsight.workers.dev/mcp'
Common questions

What is the Rugsight MCP server?

Rugsight is an MCP server listed in the public MCP registry as dev.workers.rugsight.rugsight/rugsight. Solana token rug-risk scores. Free basic score; full report pay-per-call via x402 (0.03 USDC). This page covers its hosted endpoint (https://rugsight.rugsight.workers.dev/mcp).

Is the Rugsight MCP server safe to use?

Rugsight scores 68 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 Rugsight MCP server expose?

Rugsight exposes 2 tools: get_token_risk_score, get_token_risk_report. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.

Does the Rugsight MCP server require authentication?

No. We connected to Rugsight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Rugsight MCP server still maintained?

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