Skip to content

SA Crypto Tax Rules MCP server

za.co.aiagenttools/cryptotaxaiagenttools.co.zastreamable-httpv1.0.1Scanned

SA crypto tax: FIFO capital gains, tax estimates, CGT exclusion, capital vs revenue, CARF

5 tools: 4 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 4 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 0
  • 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.dev only lists and labels, and these labels are the same either way.

What the SA Crypto Tax Rules MCP server can do

The SA Crypto Tax Rules MCP server is published by aiagenttools.co.za, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: crypto_gains_fifo, crypto_tax_estimate, crypto_capital_or_revenue and unmet_request), but cannot delete data. 1 tool only reads.

1 tool reads private data (crypto_tax_rules).

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.

Last scanned Nov 8, 2026, version 1.0.1.

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
  • crypto_capital_or_revenueGives a reasoned indication of whether a South African taxpayer's crypto gains are likely capital (CGT, 40% inclusion) or revenue (fully taxed as income), using the factors SARS an…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
    Gives a reasoned indication of whether a South African taxpayer's crypto gains are likely capital (CGT, 40% inclusion) or revenue (fully taxed as income), using the factors SARS and the courts weigh: intention, holding period, trading frequency, how it is funded and whether it is run like a business. An indicator for discussion, not a ruling.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • crypto_gains_fifoCalculates South African capital gains and losses on crypto from a list of buys, sells, crypto-to-crypto swaps, spends, gifts and crypto income, using first-in-first-out (SARS acce…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
    Calculates South African capital gains and losses on crypto from a list of buys, sells, crypto-to-crypto swaps, spends, gifts and crypto income, using first-in-first-out (SARS accepts FIFO or specific identification; weighted average is not allowed). Returns each disposal's proceeds, base cost and gain, totals per tax year (1 March – end February), income to declare, and holdings left with their base cost. Optionally estimates the tax per year.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • crypto_tax_estimateEstimates the extra South African income tax caused by crypto in one tax year, for an individual, company or trust: applies the CGT annual exclusion (R50,000 for individuals from 1…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
    Estimates the extra South African income tax caused by crypto in one tax year, for an individual, company or trust: applies the CGT annual exclusion (R50,000 for individuals from 1 March 2026), the 40% or 80% inclusion rate, the tax tables and age rebates, and shows tax with and without the crypto, the marginal rate and any capital loss to carry forward.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • unmet_requestFree to call.No findings

    Why it is in this group

    • The name "unmet_request" says "request": a word for a change.
    Description, as the server wrote it
    Free to call. If you needed South African data that none of these tools provide (a cost, rate, rule, price or place we don't cover), describe it here in one sentence. We review these every week and build the most-requested data first.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • crypto_tax_rulesReturns the South African crypto tax rules for a tax year: income tax table and rebates, CGT annual exclusion, inclusion rates and maximum effective rates, company and trust rates,…Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "table": it reads databases.
    Description, as the server wrote it
    Returns the South African crypto tax rules for a tax year: income tax table and rebates, CGT annual exclusion, inclusion rates and maximum effective rates, company and trust rates, accepted cost methods (FIFO or specific identification; not weighted average), how swaps, spending, income and gifts are treated, and SARS reporting under CARF.

    Annotations the server declares

    • readOnlyHint: 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 untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 9, 2026, 07:20 UTC, unchanged since Nov 9, 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://aiagenttools.co.za/cryptotax/mcp: tools/list returned 5 tools to an anonymous client, including crypto_gains_fifo (write), crypto_tax_estimate (write), crypto_capital_or_revenue (write), unmet_request (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http cryptotax https://aiagenttools.co.za/cryptotax/mcp
claude mcp add --transport http cryptotax https://aiagenttools.co.za/cryptotax/mcp

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__cryptotax__crypto_tax_rules"
    ],
    "ask": [
      "mcp__cryptotax__crypto_gains_fifo",
      "mcp__cryptotax__crypto_tax_estimate",
      "mcp__cryptotax__crypto_capital_or_revenue",
      "mcp__cryptotax__unmet_request"
    ],
    "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 cryptotax. Review it before you use it.

Capability tags behind 1 rule
  • mcp__cryptotax__crypto_tax_rules private-data

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://anlyon.dev/api/v1/servers/za.co.aiagenttools/cryptotax/verify?hash=094a7e3bf948419f5349127cbb5c144cdceea172fdebc7cd358896fd4e3acaa2" | jq -e '.changed == false'

Pinned hash 094a7e3bf948, from Nov 8, 2026, 10:19 UTC.

Watch

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

https://anlyon.dev/servers/za.co.aiagenttools/cryptotax/changes.xml

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

Badge

anlyon.dev badge for za.co.aiagenttools/cryptotax
[![anlyon.dev](https://anlyon.dev/badge/za.co.aiagenttools/cryptotax.svg)](https://anlyon.dev/servers/za.co.aiagenttools/cryptotax)

Source: MCP Registry. Synced Nov 8, 2026, 10:18 UTC.

SA Crypto Tax Rules MCP server: questions and answers

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

Is the SA Crypto Tax Rules 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 SA Crypto Tax Rules MCP server delete data?

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

Can the SA Crypto Tax Rules 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 SA Crypto Tax Rules MCP server have?

5 tools: 4 write, 1 read. crypto_gains_fifo, crypto_tax_estimate, crypto_capital_or_revenue, unmet_request and crypto_tax_rules.

Does the SA Crypto Tax Rules MCP server need sign-in or OAuth?

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

Does the SA Crypto Tax Rules MCP server send data to outside services?

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

Has the SA Crypto Tax Rules MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 8, 2026.