_ registry / mcp + a2a JSONRPC · checked 2h ago

getlawed-sa-law

https://getlawed.co.za

Registry code: c3c6d23887f5abb1

api record

GetLawED — verified South African law. Searches GetLawED's library of OFFICIAL South African legal texts: Constitutional Court, SCA, High Court, Labour, Land, Tax and tribunal judgments; Acts split into sections; regulations, rules and codes issued under them; municipal by-laws and land use schemes; Bills and Government Gazettes — each with its official source link and gazette reference.

Use legal_library_search for South African legal or tax questions, then legal_get_section to read and quote the exact provision, and legal_verify_citations to check any South African case citation or Act…

endpoint
https://getlawed.co.za/api/mcp/law/a2a
door code
5f510a80d5302623
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 getlawed-sa-law live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is getlawed-sa-law free to use?
Yes — the hub reached it with no key and no payment.
What tools does getlawed-sa-law have?
2 tools: Verify South African citations, Search official South African law.
Is getlawed-sa-law 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
610ms

last good check

priced tools
0

of 2 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 2 tools
2 never probed 0 of 2 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.

  • legal_verify_citations unknown never probed

    Send text containing South African case citations (neutral, e.g. [1995] ZACC 3, or law-report, e.g. 1995 (3) SA 391 (CC)) or Acts; each comes back as found / mismatch / name_only / not_found / unchecked with the official source.

    south africalawcitationsverificationhallucination check

  • legal_library_search unknown never probed

    Send a question or keywords; returns matching provisions (section-level) and judgments with short quotes, gazette references and official source links.

    south africalawlegislationregulationsby-lawscase lawtax

_ 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 c3c6d23887f5abb1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c3c6d23887f5abb1/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/c3c6d23887f5abb1/badge.svg)](https://brick.blue/agent/c3c6d23887f5abb1?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
70%

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
3,767ms
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.