io.github.sturs49/cryptotaxedge
REMOTE · MCP.CRYPTOTAXEDGE.COM · SCANNED SEP 29
US tax classification for on-chain transactions: category, treatment, confidence, review flags.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 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 1295 tokens (~215/item across 6 items; 4 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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
claude mcp add --transport http sturs49-cryptotaxedge 'https://mcp.cryptotaxedge.com/'
{
"mcpServers": {
"sturs49-cryptotaxedge": {
"url": "https://mcp.cryptotaxedge.com/"
}
}
} {
"servers": {
"sturs49-cryptotaxedge": {
"type": "http",
"url": "https://mcp.cryptotaxedge.com/"
}
}
} [mcp_servers.sturs49-cryptotaxedge] url = "https://mcp.cryptotaxedge.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sturs49-cryptotaxedge": {
"type": "remote",
"url": "https://mcp.cryptotaxedge.com/",
"enabled": true
}
}
} openclaw mcp add sturs49-cryptotaxedge --url 'https://mcp.cryptotaxedge.com/' --transport streamable-http
mcp_servers:
sturs49-cryptotaxedge:
url: "https://mcp.cryptotaxedge.com/" {
"McpServers": {
"sturs49-cryptotaxedge": {
"Transport": "http",
"Url": "https://mcp.cryptotaxedge.com/"
}
}
} assistant mcp add sturs49-cryptotaxedge -t streamable-http -u 'https://mcp.cryptotaxedge.com/'
{
"mcpServers": {
"sturs49-cryptotaxedge": {
"type": "http",
"url": "https://mcp.cryptotaxedge.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 25 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 29 Sept 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 | 23 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | cf8f165d39d1db80e7edf0890cd71f4 |
| 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. | present | 19718 | 13 | Verified |
| cryptotaxedge.com. | absent | 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 |
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/ |
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 →
classify_batch Classify transaction batch ~376
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engagement_id | string | – | (Optional) host-side engagement identifier. Reserved for firm-policy + engagement-record correlation. No effect today; forward-compatible. |
| firm_id | string | – | (Optional) host-side firm identifier. When firm classification policy is configured, applies that firm's confidence thresholds + CoA overrides. |
| transactions | array | yes | Array of transactions to classify (max 100 per call). |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
classify_transaction Classify one transaction ~427
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | 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_address | string | – | (Optional) 0x-prefixed contract address the transaction called. With function_selector + chain, performs a rule-library tuple lookup. |
| function_selector | string | – | (Optional) 0x-prefixed 4-byte function selector (first 4 bytes of tx input data). |
| tx_hash | string | – | Transaction hash (0x-prefixed 66-char for EVM, base-58 for Solana). Either tx_hash OR contract_address is required. |
| Name | Type | Req | Description |
|---|---|---|---|
| assets | object | – | 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. |
| category | string | yes | Canonical 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/… |
| confidence | integer | yes | – |
| description | string|null | – | Plain-English reasoning for the verdict, same field as REST /v1. |
| explanation | string|null | – | Deprecated alias of description, kept for existing clients. |
| ledger_action | string|null | – | Suggested ledger label for posting, same field as REST /v1. |
| needs_review | boolean | yes | – |
| protocol | string|null | – | – |
| taxable | boolean|null | – | null when needs_review |
| treatment | string | yes | Closed five-value tax treatment enum, safe to switch on exhaustively. needs_review means no treatment is asserted. |
No examples provided.
lookup_contract Look up contract metadata ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address (0x-prefixed 42-char for EVM). |
| chain | string | yes | Chain slug (e.g. "ethereum", "polygon", "arbitrum"). EVM only. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | – |
| chain | string|null | – | – |
| name | string|null | – | – |
| protocol | string|null | – | – |
No examples provided.
map_to_chart_of_accounts Map to chart of accounts ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_of_accounts | array | – | 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… |
| transactions | array | yes | Transactions to classify + map (max 100 per call). |
| Name | Type | Req | Description |
|---|---|---|---|
| account | string|null | – | – |
| mapping_basis | string|null | – | – |
No examples provided.
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 85 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 4 tools: classify_transaction, lookup_contract, classify_batch, map_to_chart_of_accounts. Their descriptions and schemas cost roughly 1,129 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 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.