SolSentry MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLSENTRY_API_KEY | No | Bearer token for authenticated endpoints | |
| SOLSENTRY_API_URL | No | API endpoint | https://api.solsentry.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_operatorA | Check the risk profile of a Solana wallet as a token operator/deployer. Returns confirmed rug count, risk label, behavioral tags, and a plain-English summary. Call this before interacting with tokens deployed by an address. |
| check_tokenA | Check the risk profile of a Solana token by mint address. Returns risk score, risk flags, operator history, and bundle detection. Call this before buying or listing any token. |
| get_top_operatorsA | Get the top Solana rug pull operators ranked by confirmed scam count. Returns a leaderboard of the worst serial deployers tracked by SolSentry. |
| get_network_statsB | Get SolSentry system-wide threat intelligence statistics: total scans, accuracy, resolve rate, operator counts, bot clusters. |
| explain_riskA | Get a human-readable explanation of why a wallet or token is risky. Accepts either a wallet address (checked as operator) or a token mint address. Returns a plain-English warning suitable for displaying to end users. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct function: checking operator risk, checking token risk, explaining risk, getting network stats, and getting top operators. There is no overlap in purpose.
All tools follow a consistent verb_noun pattern with snake_case: check_operator, check_token, explain_risk, get_network_stats, get_top_operators. The naming is predictable and uniform.
With 5 tools, the server is well-scoped for risk assessment and monitoring of Solana tokens and operators. It covers core actions without unnecessary bloat.
The tool set provides full coverage for the domain: checking operator and token risk, explaining risk, and accessing system-wide statistics and top operators. No obvious gaps for the stated purpose.