Iskra Solana Reputation

io.github.chaband-opsPublished by GitHub account chaband-opsv2.0.0Updated Oct 24, 2026

Solana wallet & token reputation lookup. Risk verdict, score, DefiLlama TVL, Rugcheck.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant look up Solana wallet and token reputation, returning a risk verdict, score, DefiLlama TVL and Rugcheck data.

What you can do
This remote MCP server provides Solana wallet and token reputation lookups. According to its description, it returns a risk verdict and score for an address or token, along with DefiLlama TVL figures and Rugcheck results. No individual tool names or parameters are listed in the supplied material.
When to use it
Useful when an assistant needs a quick risk read on a Solana wallet or token, for example before interacting with a token or explaining its reputation. It is a lookup service, not a trading or wallet-management tool.
Requirements
It is a remote streamable HTTP endpoint, so no local runtime or package install is needed. The manifest declares no authentication, environment variables or headers, so no credentials appear to be required.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to query it; consider whether the addresses you submit are sensitive. Reputation scores and verdicts are third-party assessments and should not be treated as financial advice. The server sends the queried addresses to an external service.

Installation

In SourceWeft

  1. Open Iskra Solana Reputation in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.chaband-ops%2Fiskra-reputation/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "iskra-solana-reputation": {
      "type": "http",
      "url": "https://api.iskra-bot.xyz/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.