CryptoTaxEdge MCP Server
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**US tax classification for on-chain transactions, as an MCP server.** Submit transaction
hashes and get back the canonical event category, the US tax treatment with cited
authority, a calibrated confidence score, an explicit route-to-review flag on uncertain
rows, and per-leg breakdowns with counterparty identification. 80+ chains, including
Ethereum, the major L2s, and Solana.
This is a **remote** MCP server — nothing to install or run locally.
- **Endpoint:** https://mcp.cryptotaxedge.com/ (streamable HTTP, JSON-RPC 2.0)
- **Auth:** Authorization: Bearer YOUR_API_KEY — free self-serve Developer key
(no card) at dashboard.cryptotaxedge.com
under Settings → API Keys
- **Docs:** dashboard.cryptotaxedge.com/api
- **Site:** cryptotaxedge.com
What it returns
Every classification carries the reliability envelope:
| Field | Meaning |
|---|---|
| category | Canonical event type (swap, liquidity_add, reward, bridge, ...) |
| treatment | Closed enum: disposal, income, non_taxable, expense, needs_review |
| taxable | true, false, or null — null always travels with needs_review: true |
| confidence | Routing signal: how strongly independent evidence agreed |
| needs_review | The honesty contract — uncertain rows are flagged, never guessed |
| grey_area | On contested treatments (LP, wrap, liquid staking): the position not taken |
| assets | Per-leg sent/received breakdown with counterparties |
Plain transfers, approvals, spam, failed and unsupported transactions, and every repeat
come back fully identified at no charge.
Try it
List the tools:
Classify a batch (up to 100 per call):
The same engine is available over plain REST — see the
API docs and the
developer quickstart.
Registry manifest
server.json — published to the official
MCP Registry as
io.github.sturs49/cryptotaxedge.
Listed on Glama
(glama.json).
License
MIT © 2026 Kevin Stursberg / CryptoTaxEdge. This repository is the
public listing (docs, registry manifest, and a small catalog proxy). The
classification engine is the remote server above, not this repo.
Glama / local container
Glama grades Tool Definition Quality from a container that starts and answers
MCP initialize + tools/list. The image is a tiny Node proxy — it does not
ship the engine. Catalog methods are forwarded to https://mcp.cryptotaxedge.com/.
- **Listen port:** 8080 (override with PORT; binds 0.0.0.0)
- **Paths:** POST / and POST /mcp (streamable HTTP / JSON-RPC)
- **Health:** GET / or GET /health
- No API key for initialize, tools/list, or ping
- tools/call returns **401** unless CTE_API_KEY is set or the request
already has Authorization: Bearer …
If Glama generates a Dockerfile and wraps CMD with mcp-proxy --, set the