{
  "markdown": "# @pipeworx/abn-lookup\n\nBYOK. Australian Business Register lookup: resolve an ABN or ACN to the registered\nlegal entity name, entity type, ABN status, GST registration, address state/postcode,\nand business names, or search the register by entity/business name.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1504+ live data sources.\n\n## Tools\n\n- `abn_lookup(abn, _apiKey)` — ABN -> legal name, entity type, status, GST, address, business names.\n- `abn_search(name, state?, maxResults?, _apiKey)` — entity/business name -> ranked ABN matches.\n- `acn_lookup(acn, _apiKey)` — ACN (company number) -> the same detail as `abn_lookup`.\n\n## Auth\n\nBYO only. There is no platform key. Every call requires the caller's own ABR\nweb-services GUID via `_apiKey`. Register free at\nhttps://abr.business.gov.au/Tools/WebServices — ABR requires accepting its Web\nServices Agreement (terms + a personal-info-sharing acknowledgement) under a\nregistered identity before it emails a GUID; that's a human consent step, so\nPipeworx does not hold or front one.\n\nWithout `_apiKey`, every tool refuses with \"requires an API key\" and points to\nthe registration URL above.\n\n## Data sources\n\n- `https://abr.business.gov.au/json/AbnDetails.aspx` — ABN or ACN detail.\n- `https://abr.business.gov.au/json/AcnDetails.aspx` — ACN detail.\n- `https://abr.business.gov.au/json/MatchingNames.aspx` — name search.\n\n## Gotchas\n\n- The JSON endpoints are JSONP: the body is wrapped as `<callback>({...})`,\n  where `<callback>` follows whatever `callback=` query param is sent\n  (defaults to `callback` if omitted — verified live). This pack strips the\n  wrapper generically by function name, not by hardcoding `callback`.\n- An invalid or unrecognised GUID returns **HTTP 200** with every core field\n  empty and a `Message` string (e.g. `\"The GUID entered is not recognised as a\n  Registered Party\"`), not an HTTP error. ABR uses the same shape for a\n  genuine not-found result, so an empty core field alongside a `Message`\n  cannot be told apart from a rejected key by the response alone — this pack\n  says so explicitly in the error rather than guessing.\n- Field names in the mapped output (`Abn`, `AbnStatus`, `EntityName`,\n  `BusinessName[]`, etc.) come from ABR's published JSON sample URLs; the\n  *populated* (successful-lookup) shape is unverified end-to-end because no\n  fleet GUID exists (BYOK, ruled 2026-09-03). The raw ABR payload is always\n  returned as `raw` so a caller with a real key is never blocked by a stale\n  field name here.\n- `state` on `abn_search` is a client-side filter over ABR's returned\n  matches (by each match's `State` field), not a documented ABR query\n  parameter — ABR's public JSON sample docs don't show a state filter param\n  for `MatchingNames.aspx`.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"abn-lookup\": {\n      \"url\": \"https://gateway.pipeworx.io/abn-lookup/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/abn-lookup/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1504+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Abn Lookup data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4825,
  "sha": "d2366ae4166a386c09e2e1724dd70aa2650c3303e5614e888089d59d9769189e",
  "repo_slug": "pipeworx-io/mcp-abn-lookup",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_abn_lookup_f7ac8ace/readme"
}