Search / io.github.sturs49/cryptotaxedge
cryptotaxedge
R0· no sign-inUS tax classification for on-chain transactions: category, treatment, confidence, review flags.
v1.0.0 · active · website · descriptor JSON · versions
Search / io.github.sturs49/cryptotaxedge
R0· no sign-inUS tax classification for on-chain transactions: category, treatment, confidence, review flags.
v1.0.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"cryptotaxedge": {
"type": "http",
"url": "https://mcp.cryptotaxedge.com/"
}
}
}claude mcp add --transport http cryptotaxedge https://mcp.cryptotaxedge.com/[mcp_servers.cryptotaxedge]
url = "https://mcp.cryptotaxedge.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cryptotaxedge": {
"type": "remote",
"url": "https://mcp.cryptotaxedge.com/",
"enabled": true
}
}
}{
"mcpServers": {
"cryptotaxedge": {
"type": "http",
"url": "https://mcp.cryptotaxedge.com/"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=cryptotaxedge&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmNyeXB0b3RheGVkZ2UuY29tLyJ9"
}{
"servers": {
"cryptotaxedge": {
"type": "http",
"url": "https://mcp.cryptotaxedge.com/"
}
}
}{
"mcpServers": {
"cryptotaxedge": {
"httpUrl": "https://mcp.cryptotaxedge.com/"
}
}
}extensions:
"cryptotaxedge":
enabled: true
name: "cryptotaxedge"
type: streamable_http
uri: "https://mcp.cryptotaxedge.com/"
timeout: 300
protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length2 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations4 of 4 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: classify_transaction (destructiveHint); classify_batch (destructiveHint); lookup_contract (destructiveHint); …tools.token_costabout 1,746 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+website +reachable +uptime-97% ~updated-76d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.cryptotaxedge.com/ streamable-http | none | yes | 97% | 182 ms | 2025-03-26 | 2026-10-19 |
classify_batchread-only | 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. |
classify_transactionread-only | 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. |
lookup_contractread-only | 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. |
map_to_chart_of_accountsread-only | 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. |
Schemas: list_tools.
{
"name": "io.github.sturs49/cryptotaxedge",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.cryptotaxedge.com/",
"type": "streamable-http"
}
],
"version": "1.0.0",
"websiteUrl": "https://mcp.cryptotaxedge.com",
"description": "US tax classification for on-chain transactions: category, treatment, confidence, review flags."
}