# io.github.sturs49/cryptotaxedge

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** io.github.sturs49
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.cryptotaxedge.com/
- **Source:** https://mcp.cryptotaxedge.com
- **Endpoint health:** reachable (last checked 2026-09-23T05:12:08.488Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-23T05:12:08.488Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.
**Findings**
- injection-shaped content (note) in the `classify_transaction` tool: Links to undeclared domain: cryptotaxedge.com
- injection-shaped content (note) in the `classify_batch` tool: Links to undeclared domain: cryptotaxedge.com

## Tools

4 declared. Observed from a live `tools/list` probe.
- `classify_transaction` — Classify a single blockchain transaction using CryptoTaxEdge's multi-source consensus engine, the same engine and serve semantics as the public REST /v1/classif
- `lookup_contract` — Look up a smart contract in CryptoTaxEdge's registry. Returns protocol metadata, contract type, verified ABI availability, label, and category hints. Use before
- `classify_batch` — Classify a batch of blockchain transactions (up to 100) using CryptoTaxEdge's classification engine. Built for accounting platforms integrating CryptoTaxEdge as
- `map_to_chart_of_accounts` — Map classified blockchain transactions into journal-entry-ready ledger lines against a chart of accounts. For each transaction (up to 100): debit account, credi

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"cryptotaxedge\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.cryptotaxedge.com/\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.sturs49%2Fcryptotaxedge
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.sturs49%2Fcryptotaxedge/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.sturs49%2Fcryptotaxedge
- HTML page: https://forgeregistry.com/registry/io.github.sturs49%2Fcryptotaxedge
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.