The MCP server for crypto tax classification
Connect Claude Desktop or any MCP-capable agent to the CryptoTaxEdge engine and tax classification becomes a tool call: the canonical category, the US tax treatment, a confidence score, and an honest review flag. Same engine, same wire values as the REST API; MCP is the delivery format built for agents: instead of an agent guessing a treatment from the transaction data, it gets the engine's classification with evidence, and an honest needs-review flag when the answer genuinely requires a human. How we measure that difference.
Three tools
| Tool | What it does |
|---|---|
classify_batch | The flagship. Up to 100 transaction hashes per call; each result carries category, treatment, taxable, confidence, review routing, and per-leg detail when a complex transaction decomposes. |
classify_transaction | Single-transaction lookup against the classification cache; on a miss it tells the agent how to run the full analysis instead of guessing. |
lookup_contract | Protocol, label, and category metadata for a contract address. |
Connect
The server speaks JSON-RPC 2.0 over HTTPS at https://mcp.cryptotaxedge.com/, authenticated with a Bearer API key. The free Developer tier (250 billable transactions/month, no card) covers agent experiments; keys mint at dashboard.cryptotaxedge.com/settings. A machine-readable server card lives at /.well-known/mcp.json.
Why agents need a determination layer
An agent that guesses tax treatment is a liability. The engine returns needs_review with taxable: null when the evidence does not support a confident answer, and a 502 from an upstream source is never shipped as a classification. Your agent inherits that honesty contract instead of improvising around it; grey-area categories even return the documented house position and the alternative, so the agent can present both.
Every response validates against the published cte-classification-v1 schema, and verbatim wire captures show exactly what comes back, deferrals included.
FAQ
What tools does the CryptoTaxEdge MCP server expose?
Three: classify_batch (up to 100 transaction hashes per call, returning category, US tax treatment, confidence, and review routing per transaction), classify_transaction (single-transaction cache lookup), and lookup_contract (protocol and label metadata for a contract address).
How do I connect an AI agent to CryptoTaxEdge?
Add it as a remote MCP server: the endpoint is https://mcp.cryptotaxedge.com/ speaking JSON-RPC 2.0 over HTTPS, authenticated with a Bearer API key. The free Developer tier includes 250 billable transactions per month with no card required. A machine-readable server card is published at /.well-known/mcp.json.
Does the MCP server return the same results as the REST API?
Yes. Both surfaces run the same classification engine and return identical wire values: category, treatment, taxable, confidence, needs_review, and grey-area positions. MCP is a delivery format for agents, not a different product.
What happens when a transaction cannot be classified confidently?
The engine returns needs_review with taxable set to null instead of asserting an outcome, so the agent inherits an honest deferral rather than a guess.
Not tax advice. CryptoTaxEdge is software, not a licensed tax advisor. Classifications are informational only. Verify results and consult a qualified tax professional before filing.