Skip to main content
Glama
Sign In
solana-auditor

solana-auditor

by jdjdjjdrjnsn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to solana-auditor

No user-submitted related servers found.

    Related Servers

    • Watchdog

      OxToF
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to run pre-signature security checks: identifying who can replace a Solana program's code or control an EVM contract's upgrades, surfacing dependency advisories for lockfiles, scanning public repos before release, and setting 30-day signed-webhook alerts on changes. Calls are paid per use in USDC over x402 from a wallet with per-call caps and a session budget.
      8
      58 npm
      MIT

    • pyresec

      renaat-s
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible agents to submit source code for automated SAST/SCA security audits paid via x402 USDC micropayments on Base, returning structured vulnerability findings, CWE IDs, and optional remediated code patches.
      MIT

    • solidity-sentinel

      Baneado98
      A
      license
      A
      quality
      C
      maintenance
      Enables static security audit of Solidity smart contracts by analyzing source code or deployed bytecode for vulnerabilities, providing risk scores and detailed findings.
      1
      MIT

    • Agentic Smart Contract

      Alpha-Park
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables static auditing of EVM Solidity smart contracts to detect critical vulnerabilities such as reentrancy state changes, unhandled external calls, unchecked delegatecall, and tx.origin authentication flaws, producing risk audit reports.
      7
      -
    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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one audits Solana code, the other generates payment invoices. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (audit_solana_code, get_payment_invoice), making the naming predictable and clear.

    Tool Count3/5

    With only two tools, the server feels thin. The payment invoice tool is tangential to the core auditing purpose, making the tool count borderline for the stated domain.

    Completeness3/5

    The audit surface is minimal with only a single audit operation, lacking supporting features like audit history or status retrieval. The inclusion of payment invoicing is odd and doesn't fill functional gaps in the auditing workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources