io.github.sturs49/cryptotaxedge

Est-ce que io.github.sturs49/cryptotaxedge est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.sturs49/cryptotaxedge » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• classify_batch≈ 1106 tokens

  Classify a batch of blockchain transactions (up to 100) using CryptoTaxEdge's classification engine. Built for accounting platforms integrating CryptoTaxEdge as their classification layer. Returns per-transaction: category (the open vocabulary the engine emits, for example swap, transfer, staking, reward, airdrop, income_receipt, fee_payment, borrow, repay, collateral_supply, collateral_withdraw, liquidity_add, liquidity_remove, wrap, unwrap, liquid_staking_mint, bridge_transfer, nft_mint, spam, unclassified; the full set with house treatments is at https://cryptotaxedge.com/standard/#categories and grows additively, so branch exhaustive logic on treatment, never on category), treatment (closed enum: disposal, income, non_taxable, expense, needs_review; needs_review means no treatment is asserted), tax_category (the engine's stored treatment value, kept for existing hosts), taxable, confidence score, needs_review, ledger_action, protocol, description (plain-English reasoning, also returned as explanation for existing clients), assets (sent, received, gas) and a reliability envelope with an explicit route-to-review flag. Complex multi-step transactions (flash loans, batch NFT sales, bridges, DCA programs) additionally return a per-leg breakdown and a preparer-ready memo with IRS citations. EVM + Solana. Pass engagement_id / firm_id to apply firm-specific classification policy when configured.

  Paramètres, retour & exemple (3)

  Paramètres

  • firm_id · string · optionnel
    (Optional) host-side firm identifier. When firm classification policy is configured, applies that firm's confidence thresholds + CoA overrides.
  • transactions · array · requis
    Array of transactions to classify (max 100 per call).
  • engagement_id · string · optionnel
    (Optional) host-side engagement identifier. Reserved for firm-policy + engagement-record correlation. No effect today; forward-compatible.

  Exemple d'appel

  {"name": "classify_batch", "arguments": {"transactions": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": []}}

• classify_transaction≈ 946 tokens

  Classify a single blockchain transaction using CryptoTaxEdge's multi-source consensus engine, the same engine and serve semantics as the public REST /v1/classify endpoint. Returns the /v1 contract fields: category (the open vocabulary the engine emits, for example swap, transfer, staking, reward, airdrop, income_receipt, fee_payment, borrow, repay, collateral_supply, collateral_withdraw, liquidity_add, liquidity_remove, wrap, unwrap, liquid_staking_mint, bridge_transfer, nft_mint, spam, unclassified; the full set with house treatments is at https://cryptotaxedge.com/standard/#categories and grows additively, so branch exhaustive logic on treatment, never on category), treatment (closed enum: disposal, income, non_taxable, expense, needs_review; needs_review means no treatment is asserted and taxable is null), taxable, confidence, needs_review, ledger_action, protocol, description (plain-English reasoning, also returned as explanation for existing clients) and, on hash lookups, assets (sent, received, gas). Works for EVM chains and Solana. Provide tx_hash (chain optional, auto-detected), or contract_address + function_selector + chain for a rule-library tuple lookup.

  Paramètres, retour & exemple (4)

  Paramètres

  • chain · string · optionnel
    Chain slug (e.g. "ethereum", "polygon", "bsc", "arbitrum", "base", "optimism", "avalanche", "solana"). Optional for tx_hash lookups; the engine auto-detects the chain. REQUIRED for contract_address lookups.
  • tx_hash · string · optionnel
    Transaction hash (0x-prefixed 66-char for EVM, base-58 for Solana). Either tx_hash OR contract_address is required.
  • contract_address · string · optionnel
    (Optional) 0x-prefixed contract address the transaction called. With function_selector + chain, performs a rule-library tuple lookup.
  • function_selector · string · optionnel
    (Optional) 0x-prefixed 4-byte function selector (first 4 bytes of tx input data).

  Exemple d'appel

  {"name": "classify_transaction", "arguments": {"chain": "texte", "tx_hash": "texte", "contract_address": "texte", "function_selector": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"assets": {}, "taxable": true, "category": "texte", "protocol": "texte", "treatment": "disposal", "confidence": 1, "description": "texte", "explanation": "texte", "needs_review": true, "ledger_action": "texte"}}

• lookup_contract≈ 229 tokens

  Look up a smart contract in CryptoTaxEdge's registry. Returns protocol metadata, contract type, verified ABI availability, label, and category hints. Use before deciding whether to classify a tx.

  Paramètres, retour & exemple (2)

  Paramètres

  • chain · string · requis
    Chain slug (e.g. "ethereum", "polygon", "arbitrum"). EVM only.
  • address · string · requis
    Contract address (0x-prefixed 42-char for EVM).

  Exemple d'appel

  {"name": "lookup_contract", "arguments": {"chain": "texte", "address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "chain": "texte", "category": "texte", "protocol": "texte"}}

• map_to_chart_of_accounts≈ 499 tokens

  Map classified blockchain transactions into journal-entry-ready ledger lines against a chart of accounts. For each transaction (up to 100): debit account, credit account, optional gain/loss plug account, memo (protocol + reasoning), confidence, and a route-to-review flag, plus category roll-ups with the governing US tax authority (IRC §1001, §61, Rev. Rul. 2019-24, Rev. Rul. 2023-14, etc.). Pass your own chart_of_accounts (array of {name, type}) and the tool maps to YOUR account names; omit it for a standard crypto-treasury chart. Suggested, non-binding entries: the ledger platform owns amounts, cost basis, and posting.

  Paramètres, retour & exemple (2)

  Paramètres

  • transactions · array · requis
    Transactions to classify + map (max 100 per call).
  • chart_of_accounts · array · optionnel
    Optional: your chart of accounts as [{name, type}]. Account names are pattern-matched per role (digital assets, income, fees, realized G/L, collateral, LP positions, loan payable). Omit for the standard chart.

  Exemple d'appel

  {"name": "map_to_chart_of_accounts", "arguments": {"transactions": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"account": "texte", "mapping_basis": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.cryptotaxedge.com/