Skip to main content
Glama
solsentry

SolSentry MCP

Official
by solsentry
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

@solsentry/mcp

npm version license

RugCheck tells you a fire is burning. SolSentry tells you who lit it.

SolSentry packages its public operator-risk intelligence surface as an MCP server, a TypeScript SDK, and a skills bundle. All interfaces use the live REST API at https://api.solsentry.app.

Live references

Precision is auditable per-mint at /v1/predictions/{mint} (live). Pull any current system numbers from the live API rather than this README — never cite a hardcoded accuracy/precision figure or operator-level aggregate as a standing fact.

  • API stats: https://api.solsentry.app/v1/stats

  • NPM: https://www.npmjs.com/package/@solsentry/mcp

  • GitHub org: https://github.com/solsentry

Related MCP server: token-rugcheck

Interfaces

Surface

Use it when

Entry

MCP server

AI agents (Claude Desktop, Cursor, Claude Code, any MCP client)

npx @solsentry/mcp

TypeScript SDK

TS backends, bots, wallets, dApps that don't speak MCP

import { SolSentryClient } from "@solsentry/mcp/client"

Skills bundle

Claude Code / Cursor with the Agent Skills spec

npx skills add @solsentry/mcp

All three call the public REST API at api.solsentry.app. No API key required for read endpoints.

Numbers drift daily as predictions resolve — verify live: curl https://api.solsentry.app/v1/stats

What's in this repo

solsentry-mcp/
├── src/                            ← TypeScript source (MCP server + SDK)
├── skills/
│   └── solsentry-postdeploy/       ← 1 skill, 6 references (progressive disclosure)
│       ├── SKILL.md                  orchestrator: when to load each reference
│       └── references/
│           ├── threat-intel.md     · generic risk lookup
│           ├── counterparty.md     · pre-CPI counterparty check
│           ├── monitor.md          · post-deploy program monitoring
│           ├── forensics.md        · post-incident drain trace
│           ├── token-launch.md     · pre-launch readiness for your own token
│           └── cluster-graph.md    · operator/bot network exploration
└── docs/                           ← public reference docs
    ├── risk-scoring.md             · scoring methodology + thresholds
    ├── flags.md                    · canonical flag glossary
    ├── openapi.yaml                · machine-readable REST spec
    └── x402-example.md             · paid endpoint integration example

SolSentry monitors Solana mainnet continuously and tracks serial rug pull operators, bot clusters, and malicious token launches. The data is refreshed every 30 seconds and available to any client that speaks MCP or plain HTTP.

Quick start

npx -y @solsentry/mcp

Claude Desktop

{
  "mcpServers": {
    "solsentry": {
      "command": "npx",
      "args": ["-y", "@solsentry/mcp"]
    }
  }
}

Cursor / Claude Code

{
  "mcpServers": {
    "solsentry": {
      "command": "npx",
      "args": ["-y", "@solsentry/mcp"]
    }
  }
}

Tools

Tool

Purpose

check_operator

Risk profile of a wallet as a token deployer

check_token

Risk profile of a token mint

get_top_operators

Leaderboard of serial ruggers

get_network_stats

System-wide public metrics

explain_risk

Plain-language summary for a wallet or mint

TypeScript SDK

import { SolSentryClient } from "@solsentry/mcp/client";

const client = new SolSentryClient();
const stats = await client.get("/v1/stats");
console.log(stats);

REST API

curl https://api.solsentry.app/v1/stats
curl https://api.solsentry.app/v1/operator/<wallet-address>
curl https://api.solsentry.app/v1/top-operators?limit=5

Configuration

Environment variable

Default

Purpose

SOLSENTRY_API_URL

https://api.solsentry.app

API endpoint

SOLSENTRY_API_KEY

—

Bearer token for authenticated endpoints

Notes

  • Public quality claim: precision is auditable per-mint at /v1/predictions/{mint} (live) — re-verify on the day; never ship a hardcoded precision number.

Requirements

  • Node.js >= 18

License

MIT

Links + Contact

Install Server
A
license - permissive license
A
quality
B
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/solsentry/solsentry-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server