Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.sturs49/cryptotaxedge

REMOTE · MCP.CRYPTOTAXEDGE.COM

US tax classification for on-chain transactions: category, treatment, confidence, review flags.

0 this week 86 Trust /100

Last scanned (20 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2421 tokens (~345/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Nov 26 0
    • Tool “classify_batch” rewrote its description, which is the text the model reads security
    • Tool “classify_transaction” rewrote its description, which is the text the model reads security
    • Schema quality: 295 → 345 ▼ functional
    • “classify_batch” added an optional parameter “prices” cosmetic
    • “classify_transaction” added an optional parameter “prices” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
    • Schema quality: 234 → 295 ▼ functional
    • “classify_batch” added an optional parameter “wallet” cosmetic
    • “classify_batch” added an optional parameter “wallets” cosmetic
    • “classify_transaction” added an optional parameter “wallet” cosmetic
    • “classify_transaction” added an optional parameter “wallets” cosmetic
    • “map_to_chart_of_accounts” added an optional parameter “wallet” cosmetic
    • “map_to_chart_of_accounts” added an optional parameter “wallets” cosmetic
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −3
    • Authorization: pass → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1295 → 1641 ▼ functional
    • New tool “verify_batch” functional
  • 22 Oct 26 0
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
    • Server version: 0.2.2 → 0.3.0 functional
  • 3 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.cryptotaxedge.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cryptotaxedge.com CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 d174d8b2badfae60e126eaa76014ec8
SANs: cryptotaxedge.com, mcp.cryptotaxedge.com, *.mcp.cryptotaxedge.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.cryptotaxedge.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
cryptotaxedge.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="CryptoTaxEdge MCP"

Bearer realm="CryptoTaxEdge MCP"

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.cryptotaxedge.com/ Verified 200
http (plaintext) http://mcp.cryptotaxedge.com/ HTTPS enforced 301 https://mcp.cryptotaxedge.com/
MCP tools · 5 exposed · ~2,211 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
classify_batch ~686

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, plus block_time and block_number. A multi-step lending transaction (Morpho Blue, Aave V3) additionally returns a per-leg breakdown (legs) and a summary (memo). Pass prices: true for an indicative USD value per asset and a valuation block. EVM + Solana. Rules for using the answer: never book a row whose needs_review is true, and never treat legs as a verdict (they are a proposal for a reviewer and do not change the row). A row that carries error was not classified: it is not a review decision, so fix or resend the input. Pass engagement_id / firm_id to apply firm-specific classification policy when configured.

NameTypeReqDescription
engagement_idstring–(Optional) host-side engagement identifier. Reserved for firm-policy + engagement-record correlation. No effect today; forward-compatible.
firm_idstring–(Optional) host-side firm identifier. When firm classification policy is configured, applies that firm's confidence thresholds + CoA overrides.
pricesboolean–(Optional) true to add an indicative USD value to each asset: usd_price and usd_value on every leg that can be priced, at the market price near the block time, plus a valuation block. Not a cost basi…
transactionsarrayyesArray of transactions to classify (max 100 per call).
walletstring–(Optional) One 0x-prefixed EVM address to read every transaction in this batch from. Sent and received are then reported from this address instead of from the transaction sender. Use it when the book…
walletsarray–(Optional) Up to 50 0x-prefixed EVM wallet addresses that belong to the same owner as the books. A transfer between two wallets on this list is served as an own-wallet movement (non-taxable); without…
NameTypeReqDescription
resultsarrayyes–

No examples provided.

classify_transaction ~789

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), block_time and block_number, and for a multi-step lending transaction a per-leg breakdown (legs, memo). Rules for using the answer: never book a row whose needs_review is true, and never treat legs as a verdict (they are a proposal for a reviewer and do not change the row). A row that carries error was not classified: it is not a review decision, so fix or resend the input. Pass prices: true for an indicative USD value per asset. Works for EVM chains and Solana. Provide tx_hash (chain optional, auto-detected) to classify a transaction. Without a tx_hash, contract_address + function_selector + chain asks what that contract function generally is; that answer is not about any transaction of yours, and a transfer is never answered that way. If both are sent, the tx_hash is used.

NameTypeReqDescription
chainstring–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 l…
contract_addressstring–(Optional) 0x-prefixed contract address the transaction called. With function_selector + chain, performs a rule-library tuple lookup.
function_selectorstring–(Optional) 0x-prefixed 4-byte function selector (first 4 bytes of tx input data).
pricesboolean–(Optional) true to add an indicative USD value to each asset: usd_price and usd_value on every leg that can be priced, at the market price near the block time, plus a valuation block. Not a cost basi…
tx_hashstring–Transaction hash (0x-prefixed 66-char for EVM, base-58 for Solana). Either tx_hash OR contract_address is required.
walletstring–(Optional) One 0x-prefixed EVM address to read the transaction from. Sent and received are then reported from this address instead of from the transaction sender. Use it when the books belong to some…
walletsarray–(Optional) Up to 50 0x-prefixed EVM wallet addresses that belong to the same owner as the books. A transfer between two wallets on this list is served as an own-wallet movement (non-taxable); without…
NameTypeReqDescription
assetsobject–Net asset movements, same shape as REST /v1: sent and received legs plus the gas leg (null when not attributable). Present when the engine response carries them.
block_numberinteger–The block (or Solana slot) the transaction was mined in.
block_timestring–When the transaction was mined, UTC. Absent when it could not be read.
categorystringyesCanonical category. Open vocabulary that only grows additively; tolerate unfamiliar values and branch exhaustive logic on treatment instead. Full set with house treatments: https://cryptotaxedge.com/…
chainstring|null––
confidenceintegeryesRouting signal, not an accuracy claim. 0 on a row that carries error: no verdict exists.
descriptionstring|null–Plain-English reasoning for the verdict, same field as REST /v1.
errorstring–Present only on a row the engine did not classify (invalid_hash, tx_not_retrievable, batch_budget_exhausted and similar). Such a row is not a verdict: do not post it and do not treat it as a review d…
example_tx_hashstring|null–Contract-and-selector lookups only: the classified transaction this general answer was taken from. It is not a transaction of yours.
explanationstring|null–Deprecated alias of description, kept for existing clients.
hashstring|null–The transaction hash this row answers.
ledger_actionstring|null–Suggested ledger label for posting, same field as REST /v1.
legsarray–Only when the receipt shows this wallet changing a lending position in two or more steps: one leg per event (flash_loan, supply_collateral, withdraw_collateral, borrow, repay) and a swap when market…
lookupstring–contract_function on a contract-and-selector lookup. Absent on a transaction answer.
memostring–Present with legs: a plain-English summary of them.
needs_reviewbooleanyes–
notestring–Contract-and-selector lookups only: what the answer is and is not.
protocolstring|null––
review_notestring|null–Why a review row was routed to a human.
taxableboolean|null–null when needs_review
treatmentstringyesClosed five-value tax treatment enum, safe to switch on exhaustively. needs_review means no treatment is asserted.
tx_hashstring|null–Same value as hash, kept for existing clients.
tx_idstring|null–Batch rows: your row id echoed back.
valuationobject–Only when prices: true was passed: what the usd_value figures on the legs are (currency, as_of, priced and unpriced leg counts, and a reason for each unpriced leg). Indicative market prices, not a co…

No examples provided.

lookup_contract ~93

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.

NameTypeReqDescription
addressstringyesContract address (0x-prefixed 42-char for EVM).
chainstringyesChain slug (e.g. "ethereum", "polygon", "arbitrum"). EVM only.
NameTypeReqDescription
addressstring|null––
categorystring|null–A registry hint about what the contract is for. Not a transaction category and not a tax verdict.
chainstring|null––
foundbooleanyesBranch on this: false means the address is not in the registry, and the other fields are empty.
labelstring|null––
protocolstring|null––

No examples provided.

map_to_chart_of_accounts ~341

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.

NameTypeReqDescription
chart_of_accountsarray–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 stand…
transactionsarrayyesTransactions to classify + map (max 100 per call).
walletstring–(Optional) One 0x-prefixed EVM address to read every transaction from, when the books belong to someone other than the transaction sender (for example the recipient). Same meaning as on the classify…
walletsarray–(Optional) Up to 50 0x-prefixed EVM wallet addresses that belong to the same owner as the books. A transfer between two wallets on this list is an own-wallet movement (no entry) instead of a review.…
NameTypeReqDescription
category_rollupsarray––
disclaimerstring––
errorstring––
journal_linesarray––
summaryobject–transactions, mapped, no_entry, route_to_review, not_classified (rows the engine did not classify: not reviews, fix or resend them), accounts_used (role to account name or null), chart_supplied, acco…

No examples provided.

verify_batch ~302

Verify a batch of caller-assigned transaction labels (up to 100) against CryptoTaxEdge's deterministic classification basis: rules, the verified cache and the answer guards, with no model call. Returns per row a verdict (agree, disagree, unverifiable), the engine's cte_category, cte_treatment and cte_taxable when known, confidence (a routing signal, not an accuracy claim), evidence (the checks run: label mapping, basis, legs vs on-chain transfers, label vs token flows, protocol registry, taxability, calibration), a suggested_fill and a machine-readable dispute (dispute_id, failed check, evidence, how to contest, review_sla_hours) on disagree, and a reason with fill_available on unverifiable. A row with no deterministic basis is unverifiable and free; pass fill=true on that row to run the classification engine on it (that row is then a fill). Labels are read in the Standard vocabulary (https://cryptotaxedge.com/standard/#categories), the served ledger-action labels, and the Koinly and CoinTracker export vocabularies; an unmapped label is unverifiable (label_unmapped), never best-effort matched. Verify does not decide tax treatment beyond the published Standard and does not file.

NameTypeReqDescription
fillboolean–(Optional, default false) default for rows that do not set fill.
rowsarrayyesRows to verify (max 100 per call).
NameTypeReqDescription
latency_msinteger––
meteredobject––
resultsarrayyes–

No examples provided.

Install

How do I install the io.github.sturs49/cryptotaxedge MCP server?

io.github.sturs49/cryptotaxedge is a hosted endpoint at https://mcp.cryptotaxedge.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.cryptotaxedge.com

# add to Claude Code
claude mcp add --transport http sturs49-cryptotaxedge 'https://mcp.cryptotaxedge.com/'
Common questions

What is the io.github.sturs49/cryptotaxedge MCP server?

io.github.sturs49/cryptotaxedge is an MCP server listed in the public MCP registry as io.github.sturs49/cryptotaxedge. US tax classification for on-chain transactions: category, treatment, confidence, review flags. This page covers its hosted endpoint (https://mcp.cryptotaxedge.com/).

Is the io.github.sturs49/cryptotaxedge MCP server safe to use?

io.github.sturs49/cryptotaxedge scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.sturs49/cryptotaxedge MCP server expose?

io.github.sturs49/cryptotaxedge exposes 5 tools: classify_transaction, lookup_contract, classify_batch, map_to_chart_of_accounts, verify_batch. Their descriptions and schemas cost roughly 2,211 tokens of context every time the server is loaded.

Does the io.github.sturs49/cryptotaxedge MCP server require authentication?

Yes. io.github.sturs49/cryptotaxedge asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.github.sturs49/cryptotaxedge MCP server still maintained?

io.github.sturs49/cryptotaxedge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.sturs49/cryptotaxedge MCP server?

VerifyMCP ran 13 checks on io.github.sturs49/cryptotaxedge, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.