Skip to main content
Glama
sturs49

CryptoTaxEdge

by sturs49
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to CryptoTaxEdge

No user-submitted related servers found.

    Related Servers

    • Hive Tax Observer

      srotzin
      A
      license
      Not graded
      quality
      C
      maintenance
      Classifies on-chain crypto transactions into sale, swap, income, or transfer for observational tax-event tracking, surfacing cost-basis-relevant inputs.
      MIT

    • taxformatter-mcp-server

      Sean-Bravo
      A
      license
      Not graded
      quality
      C
      maintenance
      Parse crypto exchange CSVs (Coinbase, Binance, Kraken, +11 more) and bank statement PDFs (Chase, BofA, +11 more) into Koinly, TurboTax, CoinLedger, or ZenLedger formats. Free tier: 25 files/month, no credit card required.
      3 npm
      ISC

    • Crypto Tax MCP

      biggling
      A
      license
      Not graded
      quality
      D
      maintenance
      Cost basis tracking, capital gains calculation, and 1099-DA reconciliation for Claude, built on top of the Crypto Portfolio MCP data layer.
      MIT

    • ClearMarket

      JDSource
      A
      license
      Not graded
      quality
      B
      maintenance
      Reference data layer for prediction markets: resolution-clarity grades (A/B/C), named resolution sources with provenance, cross-venue linking, and per-contract eligibility screens across Kalshi and Polymarket. Open,read-only, no key required.
      3
      MIT

    • base-tx-explain

      0200project
      A
      license
      Not graded
      quality
      A
      maintenance
      Explains any Base mainnet transaction hash by returning a structured JSON with action type, assets moved, risk flags, and cost details, using deterministic on-chain decoding without LLM.
      1
      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.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    classify_transaction and classify_batch share the same core action and could be confused, though their single-vs-batch distinction is clearly described. lookup_contract and map_to_chart_of_accounts are each unambiguously distinct from the classification tools.

    Naming Consistency5/5

    All tool names follow a clear verb_noun style: classify_transaction, classify_batch, lookup_contract, and map_to_chart_of_accounts. The pattern is consistently applied and easy to predict.

    Tool Count5/5

    Four tools is well-scoped for this server's purpose: contract lookup, single classification, batch classification, and chart-of-accounts mapping. Each tool earns its place and the count stays comfortably within the ideal range.

    Completeness4/5

    The core workflow of lookup, classify, batch-classify, and map to ledger entries is well covered. The only notable gap is the absence of a reclassification or review-override tool for adjusting previous decisions, but this is a minor gap for a stateless classification API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources