Skip to main content
Glama
glittercowboy

solana-forensics

by glittercowboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to solana-forensics

No user-submitted related servers found.

    Related Servers

    • onchain-forensics

      manteclaw
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables blockchain forensics across multiple chains (Base, Ethereum, Arbitrum, Optimism, Polygon) with tools to trace transactions, cluster addresses, detect anomalies, and identify mixer usage.
      MIT

    • Solana DeFi Analytics MCP

      kirtiraj22
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive analytics and insights for Solana wallets and their DeFi activities, including transaction tracking, DeFi position monitoring, risk profiling, and strategy recommendations.
      15 npm
      7
      MIT
    • DeFade by DeFadeLtd

      DeFadeofficial

      DeFadeLtd
      A
      license
      A
      quality
      A
      maintenance
      Rug pull risk scores and on-chain forensics for memecoins on Solana, Ethereum, Base and Robinhood Chain - launch-bundle detection, funding-origin tracing, deployer history, insider networks and whale flow. 15 read-only tools.
      23
      15
      239 npm
      MIT

    • helius-forensics-mcp

      drtiibiird
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Solana wallet forensics via MCP, including tracing funds, identifying entities, scoring risk, and comparing wallets using Helius APIs.
      MIT

    • deepnets

      scifantastic
      A
      license
      B
      quality
      D
      maintenance
      Provides deep analysis of Solana tokens, their risks, and holder information.
      16
      25 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: discover lists operations, get_schema returns parameter details, execute runs an operation, and continue handles pagination. There is no ambiguity about which tool to use for a given step.

    Naming Consistency5/5

    All tools follow a consistent 'solana_forensics_<verb>' pattern (discover, get_schema, execute, continue). The naming convention is uniform and predictable, making the API easy to navigate.

    Tool Count5/5

    Four tools is well-scoped for a meta-interface. Each tool is necessary for the operation lifecycle (explore, inspect, execute, paginate), and there is no bloat or redundancy.

    Completeness5/5

    The tool set covers the full workflow: discovering available operations, fetching schemas, executing them, and continuing through paginated results. No obvious gaps exist for the stated purpose of a forensics operation interface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources