Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SA Crypto Tax Rules

REMOTE · AIAGENTTOOLS.CO.ZA

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

+3 this week 64 Trust /100

Last scanned (11 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1184 tokens (~197/item across 6 items; 6 tools + 0 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 Management43
  • Stability observed for 13 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1014 → 1184 ▼ functional
    • New tool “account_balance” functional
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 58

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://aiagenttools.co.za/cryptotax/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aiagenttools.co.za CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 39efccc66bafcac4132535ec8a3625fc
SANs: aiagenttools.co.za, *.aiagenttools.co.za
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 aiagenttools.co.za. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
za. DS published 45749 8 Verified
co.za. DS published 41369 8 Verified
aiagenttools.co.za. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aiagenttools.co.za/cryptotax/mcp Verified 200
http (plaintext) http://aiagenttools.co.za/cryptotax/mcp Inconclusive 405
MCP tools · 6 exposed · ~1,009 tokens

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 →

Tool Tokens
account_balance ~72

Free to call. Shows the plan on the API key you're using (free tier, Starter, Pro or pay-as-you-go), how much of the monthly allowance is left, the pay-as-you-go credit balance in rand, and where to top up. Without a key it shows how many free calls are left today.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crypto_capital_or_revenue ~211

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.

NameTypeReqDescription
disposals_per_yearnumber–Number of sells/swaps a year
intentionstringyesMain intention when buying
main_source_of_incomeboolean–True if crypto dealing is the person's main source of income. Default false
run_as_businessboolean–Organised like a business: trading bots, a trading company, full-time activity, marketing
typical_holding_daysnumber–Typical days an asset is held before selling
uses_borrowed_money_or_leverageboolean–True if purchases are funded with loans, margin or leveraged products. Default false

No output schema declared.

No examples provided.

crypto_gains_fifo ~193

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.

NameTypeReqDescription
estimate_taxobject–Optional: also estimate the tax per tax year
transactionsarrayyesEvery acquisition and disposal, any order (sorted by date; same-day keeps the given order). Include all earlier purchases of an asset, or the gain is overstated.
treatmentstring–capital (investor) or revenue (trader: gains taxed in full as income). Use crypto_capital_or_revenue if unsure

No output schema declared.

No examples provided.

crypto_tax_estimate ~308

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.

NameTypeReqDescription
ageinteger–Individuals: age on the last day of the tax year. Default 40
brought_forward_capital_lossnumber–Assessed capital loss from earlier years. Default 0
crypto_net_capital_gainnumber–Net capital gain (or loss, negative) on crypto held as an investment
crypto_revenue_incomenumber–Crypto amounts taxed as ordinary income: trading profits, mining, staking, crypto salary. Default 0
other_net_capital_gainnumber–Net capital gain on other assets in the same year (the exclusion is shared). Default 0
other_taxable_incomenumber–Taxable income from everything else, in rand. Default 0
tax_yearinteger–Year the tax year ends, e.g. 2027 for 1 March 2026 – 28 February 2027. Default: current tax year
taxpayerstring–Type of taxpayer: individual, company, trust or special_trust. Default individual

No output schema declared.

No examples provided.

crypto_tax_rules ~101

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.

NameTypeReqDescription
tax_yearinteger–Year the tax year ends, e.g. 2027. Default: current tax year

No output schema declared.

No examples provided.

unmet_request ~124

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.

NameTypeReqDescription
contextstring–Optional: the kind of task it was for, e.g. 'renovation quote' or 'payroll run'.
needstringyesWhat information you were looking for, in one sentence.
regionstring–Optional: province or town, if it matters.

No output schema declared.

No examples provided.

Install

How do I install the SA Crypto Tax Rules MCP server?

SA Crypto Tax Rules is a hosted endpoint at https://aiagenttools.co.za/cryptotax/mcp, 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 · aiagenttools.co.za

# add to Claude Code
claude mcp add --transport http za-co-aiagenttools-cryptotax 'https://aiagenttools.co.za/cryptotax/mcp'
Common questions

What is the SA Crypto Tax Rules MCP server?

SA Crypto Tax Rules is an MCP server listed in the public MCP registry as za.co.aiagenttools/cryptotax. SA crypto tax: FIFO capital gains, tax estimates, CGT exclusion, capital vs revenue, CARF. This page covers its hosted endpoint (https://aiagenttools.co.za/cryptotax/mcp).

Is the SA Crypto Tax Rules MCP server safe to use?

SA Crypto Tax Rules scores 64 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 SA Crypto Tax Rules MCP server expose?

SA Crypto Tax Rules exposes 6 tools: crypto_gains_fifo, crypto_tax_estimate, crypto_capital_or_revenue, crypto_tax_rules, unmet_request, account_balance. Their descriptions and schemas cost roughly 1,009 tokens of context every time the server is loaded.

Does the SA Crypto Tax Rules MCP server require authentication?

No. We connected to SA Crypto Tax Rules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SA Crypto Tax Rules MCP server still maintained?

SA Crypto Tax Rules is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SA Crypto Tax Rules MCP server?

VerifyMCP ran 11 checks on SA Crypto Tax Rules, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about SA Crypto Tax Rules: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.