_ registry / mcp + a2a JSONRPC · checked 53m ago

getaccounted-sa-tax

https://getaccounted.co.za

Registry code: 34c1b813389646aa

api record

GetAccountED — South African tax & accounting tools. Deterministic calculators and checks built on the SARS tables GetAccountED payroll uses: PAYE/UIF/SDL and net pay (sa_paye_calculate), VAT inclusive/exclusive (sa_vat_calculate), whether a supply is standard-rated, zero-rated or exempt and whether input VAT can be claimed (sa_vat_classify), SARS due dates with public holidays (sa_tax_calendar), SA ID / income tax / VAT / employer reference / company number checks (sa_validate_reference), and tax rates and thresholds by tax year (sa_tax_rates).

Every result cites its SARS table or Act section…

endpoint
https://getaccounted.co.za/api/mcp/tax/a2a
door code
b907a21fdd854f79
protocol
JSONRPC ·0.3
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is getaccounted-sa-tax live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is getaccounted-sa-tax free to use?
Yes — the hub reached it with no key and no payment.
What tools does getaccounted-sa-tax have?
6 tools: South African PAYE, UIF and net pay, South African VAT calculation, VAT treatment of a supply, SARS due dates, Check an SA ID, tax, VAT or company number, South African tax rates and thresholds.
Is getaccounted-sa-tax safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
716ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • sa_paye_calculate unknown never probed

    Send a data part {"skill":"sa_paye_calculate","arguments":{"salary":20000,"pay_date":"2026-11-25","age":40}}.

    south africapayrollpayeuifsars

  • sa_vat_calculate unknown never probed

    Inclusive ↔ exclusive at the VAT rate for the date; one amount or lines.

    south africavat

  • sa_vat_classify unknown never probed

    Standard-rated, zero-rated or exempt, and whether input VAT can be claimed, with the VAT Act section.

    south africavatinput tax

  • sa_tax_calendar unknown never probed

    EMP201, VAT201, IRP6, EMP501, ITR14 and CIPC due dates in a date range.

    south africasarsdeadlines

  • sa_validate_reference unknown never probed

    Send the number as a text part, or a data part with the skill.

    south africaid numbervat numbervalidation

  • sa_tax_rates unknown never probed

    Brackets, rebates, thresholds, medical credits, UIF/SDL, VAT rate by tax year.

    south africatax rates

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 34c1b813389646aa.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/34c1b813389646aa/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/34c1b813389646aa/badge.svg)](https://brick.blue/agent/34c1b813389646aa?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
629ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.