Skip to main content
Glama
Sign In
biccsdev

Solana Debug MCP

by biccsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Solana Debug MCP

No user-submitted related servers found.

    Related Servers

    • sortie

      srivtx
      A
      license
      Not graded
      quality
      D
      maintenance
      Extends Solana debugging to AI agents via MCP: decode transaction failures, trace CPI trees, and profile compute for any Solana transaction.
      12 npm
      MIT

    • Langfuse MCP Server

      Jaehyunr9433
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code, Codex, and Cursor to debug failing traces, sessions, and exceptions, inspect route decisions, prompts, datasets, and metrics, and control token overhead via compact output, file dumps, and selective tool loading. It supports local stdio or HTTP deployment with optional read-only mode for safer observability workflows.
      -

    • 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
    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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Solana debugging: transaction simulation, account data decoding, instruction decoding, error code lookup, and PDA verification. There is no overlap in their core functions.

    Naming Consistency4/5

    Tool names predominantly follow a verb_noun snake_case pattern (simulate_transaction, decode_account, decode_instruction). The one exception is anchor_error_lookup, which uses a noun_verb ordering but remains clear and consistent in style.

    Tool Count5/5

    Five tools is an ideal size for a specialized debugging server. Each tool addresses a specific need without redundancy, and the scope is well-defined.

    Completeness4/5

    The set covers the most common debugging tasks: simulate, decode, lookup errors, and verify PDAs. Minor gaps exist (e.g., fetching raw transaction logs or account history), but the core debugging workflow is well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources