Skip to content

cryptotaxedge MCP server

io.github.sturs49/cryptotaxedgesturs49streamable-httpv1.0.0Scanned

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

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the cryptotaxedge MCP server can do

The cryptotaxedge MCP server is published by the GitHub account sturs49. It has 5 tools. It can create or change data (4 tools: classify_transaction, classify_batch, map_to_chart_of_accounts and verify_batch), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (classify_transaction, classify_batch and verify_batch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 4Claude Code: ask
  • classify_batchClassify a batch of blockchain transactions (up to 100) using CryptoTaxEdge's classification engine.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Classify transaction batch
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • classify_transactionClassify a single blockchain transaction using CryptoTaxEdge's multi-source consensus engine, the same engine and serve semantics as the public REST /v1/classify endpoint.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Classify one transaction
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • map_to_chart_of_accountsMap classified blockchain transactions into journal-entry-ready ledger lines against a chart of accounts.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Map to chart of accounts
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • verify_batchVerify 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 n…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify caller labels
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • lookup_contractLook up a smart contract in CryptoTaxEdge's registry.No findings

    Why it is in this group

    • The name "lookup_contract" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up contract metadata
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.cryptotaxedge.com/: tools/list returned 5 tools to an anonymous client, including classify_transaction (write), classify_batch (write), map_to_chart_of_accounts (write), verify_batch (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 3 to 4
    • RFC 9728 protected resource metadata: https://mcp.cryptotaxedge.com/.well-known/oauth-protected-resource to none
    • Authorization servers: https://mcp.cryptotaxedge.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
  2. Tools1 added.+1 addedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4; RFC 9728 protected resource metadata: https://mcp.cryptotaxedge.com/.well-known/oauth-protected-resource -> none; Authorization servers: https://mcp.crypt…View diff
    • Tools that change things, listed without credentials: 3 to 4
    • RFC 9728 protected resource metadata: https://mcp.cryptotaxedge.com/.well-known/oauth-protected-resource to none
    • Authorization servers: https://mcp.cryptotaxedge.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http cryptotaxedge https://mcp.cryptotaxedge.com/
claude mcp add --transport http cryptotaxedge https://mcp.cryptotaxedge.com/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cryptotaxedge__lookup_contract"
    ],
    "ask": [
      "mcp__cryptotaxedge__classify_transaction",
      "mcp__cryptotaxedge__classify_batch",
      "mcp__cryptotaxedge__map_to_chart_of_accounts",
      "mcp__cryptotaxedge__verify_batch"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cryptotaxedge. Review it before you use it.

Capability tags behind 3 rules
  • mcp__cryptotaxedge__classify_transaction untrusted-input
  • mcp__cryptotaxedge__classify_batch untrusted-input
  • mcp__cryptotaxedge__verify_batch untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.sturs49/cryptotaxedge/verify?hash=e336461957fdcbfbd9bad31e8f8014ccfb13fa23d7140e38689f4dd8f2ea747d" | jq -e '.changed == false'

Pinned hash e336461957fd, from Nov 21, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.sturs49/cryptotaxedge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.sturs49/cryptotaxedge
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.sturs49/cryptotaxedge.svg)](https://radar.anlyon.com/servers/io.github.sturs49/cryptotaxedge)

Source: MCP Registry. Synced Oct 21, 2026, 18:49 UTC.

cryptotaxedge MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the cryptotaxedge MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the cryptotaxedge MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the cryptotaxedge MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the cryptotaxedge MCP server have?

5 tools: 4 write, 1 read. classify_transaction, classify_batch, map_to_chart_of_accounts, verify_batch and lookup_contract.

Does the cryptotaxedge MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the cryptotaxedge MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the cryptotaxedge MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.