Free remote MCP server for deterministic validation of Australian Business Numbers (ABNs) and Australian Company Numbers (ACNs). Checks identifier format and checksum with no API key required.
Scored across 3 tools
Each tool targets a distinct action-object pair: validate_abn and validate_acn handle offline checksum/format checks for different identifier types, while verify_abn performs a live registry lookup. The descriptions explicitly distinguish 'validate' (format/checksum only) from 'verify' (registry match), so an agent can select correctly.
All three tools follow a clean verb_noun snake_case pattern (validate_abn, validate_acn, verify_abn). The verb variation (validate vs verify) is intentional and semantically meaningful rather than inconsistent.
Three tools is on the thin side but defensible for a narrowly scoped identifier-validation server. Each tool earns its place, though the surface is clearly narrow.
There is an obvious asymmetry: ABN can be both checksum-validated and registry-verified, but ACN only has checksum validation with no registry-verification counterpart. This notable gap could cause agent dead ends for ACN lookups.
Validate the format and checksum of an Australian Business Number (ABN). This does not confirm that the ABN is registered or active.
Inputs: abn (required).
Validate the format and checksum of an Australian Company Number (ACN). This does not confirm that the company is registered or active.
Inputs: acn (required).
Verify an Australian Business Number (ABN) against the Australian Business Register. Returns checksum validity, registry match status, and available registry details.
Inputs: abn (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.