asic-lookup-mcp

Look up an Australian company (paid)

lookup_australian_company

Look up Australian companies by ABN, ACN, or name in the ASIC register to obtain registered name, status, entity type, registration dates, and former names.

Instructions

Costs USD 0.01 per successful lookup, paid automatically in USDC on Base from the wallet this server is configured with; a query that matches nothing is free, and so is a malformed one. Resolves an Australian company by ABN, ACN or name against the ASIC Company Register (about 4 million companies) and returns the registered name, ACN or ARBN, ABN, registration status, entity type and class, registration and deregistration dates, previous state of registration and former names. Give exactly one of abn, acn or name. It does NOT have GST status, business address, state or postcode, directors or officeholders, trading names, financial data, or anything about a sole trader or partnership that is not a registered company. It is a weekly snapshot, not the official register: ASIC Connect is authoritative for anything legal. This server stops spending at USD 10.00 in total.

Input Schema

TableJSON Schema

Name	Required	Description
`abn`	No	Australian Business Number, 11 digits. Spaces and hyphens are ignored.
`acn`	No	Australian Company Number, 9 digits. Spaces and hyphens are ignored.
`name`	No	Company name, matched as a prefix. Case insensitive, e.g. "woolworths".
`limit`	No	Maximum results for a name search, 1 to 25. Defaults to 25. Does not change the price.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	Anything the caller should know about this particular result.
`count`	Yes	Number of matching companies returned.
`found`	Yes	Whether any company matched.
`spend`	Yes	Running total against SPEND_CAP_USD for this server process.
`charged`	Yes	Whether this lookup cost money. False for a miss.
`results`	Yes	The matching company register records.
`price_usd`	Yes	What this lookup cost in USD, or null if it was free.
`attribution`	Yes	Required CC BY 3.0 AU attribution for the underlying data.
`settlement_tx`	Yes	Base transaction hash for the payment, if one settled.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses substantial behavior beyond annotations: per-lookup cost, automatic payment in USDC, free failed/malformed queries, a USD 10.00 total spend cap, weekly snapshot staleness, and non-authoritative status. This is rich, honest context that the annotations alone do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence carries essential operational, pricing, or limitation information. It is front-loaded with the most decision-relevant fact (cost) and then proceeds through behavior, outputs, exclusions, and authority without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the description covers pricing, payment mechanics, input constraints, return data, exclusions, data freshness, and authoritative alternatives. An agent has everything needed to decide whether and how to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful constraints beyond the schema: exactly one of abn/acn/name must be provided, and the limit parameter does not affect the price. These are important for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-resource pair: resolves Australian companies by ABN, ACN, or name against the ASIC Company Register. It also enumerates the exact return fields, making the tool's purpose unmistakable even with no sibling tools to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs the caller to supply exactly one of abn, acn, or name, and lists what the tool does NOT provide, such as GST status, directors, and trading names. It also names ASIC Connect as the authoritative alternative for legal matters, giving clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

lookup_australian_companyA