AU Agent Utilities
https://au-business-day.auagentutilities.workers.dev
Registry code: f3e00dbfc5fc7cc6
Australian business-day and public-holiday calculations for AI agents and applications.
from a public catalogue that lists it, not from the operator
- endpoint
- https://au-business-day.auagentutilities.workers.dev/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is AU Agent Utilities live?
- Yes — it answered the hub's last check (checked 58m ago). It answered 99% of checks over the last 30 days.
- Is AU Agent Utilities free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does AU Agent Utilities have?
- 4 tools: calculate_australian_business_date, calculate_australian_deadline, check_australian_business_day, count_australian_business_days.
- Is AU Agent Utilities 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.
90 days 99.2%· all time 99.2%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- add australian business days to a date
- check if a date is a business day
- count business days between dates
- calculate a deadline
- takes → gives
- data → data
- tools
- 4 reads
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
calculate_australian_business_date reads unknown never probed
Add or subtract Australian business days from a date for a specified state or territory. Positive numbers move forward and negative numbers move backward. The start date is excluded.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "date", "state", "business_days" ], "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Starting date in YYYY-MM-DD format" }, "state": { "enum": [ "ACT", "NSW", "NT", "QLD", "SA", "TAS", "VIC", "WA" ], "type": "string", "description": "Australian state or territory" }, "business_days": { "type": "integer", "maximum": 2000, "minimum": -2000, "description": "Number of business days to shift. Positive = forward, negative = backward, 0 = unchanged." } } }arguments 36 linescalculate_australian_deadline reads unknown never probed
Calculate an Australian deadline using either calendar days or business days, with an explicit start-date counting rule and optional rolling to the next or previous business day when the calculated date is not a business day.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "start_date", "state", "days", "day_type" ], "properties": { "days": { "type": "integer", "maximum": 3660, "minimum": -3660, "description": "Number of days. Positive moves forward, negative moves backward, 0 keeps the start date." }, "state": { "enum": [ "ACT", "NSW", "NT", "QLD", "SA", "TAS", "VIC", "WA" ], "type": "string", "description": "Australian state or territory" }, "day_type": { "enum": [ "business", "calendar" ], "type": "string", "description": "business excludes weekends/public holidays; calendar counts every calendar day" }, "start_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Starting date in YYYY-MM-DD format" }, "include_start_date": { "type": "boolean", "description": "Whether the start date counts. Defaults to false." }, "roll_if_non_business_day": { "enum": [ "none", "next", "previous" ], "type": "string", "description": "What to do if the unadjusted deadline is not a business day: none, next or previous. Defaults to none." } } }arguments 58 linescheck_australian_business_day reads unknown 12h ago
Check whether a date is a business day in an Australian state or territory and return the previous and next business day.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "date", "state" ], "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Date in YYYY-MM-DD format" }, "state": { "enum": [ "ACT", "NSW", "NT", "QLD", "SA", "TAS", "VIC", "WA" ], "type": "string", "description": "Australian state or territory" } } }arguments 29 linescount_australian_business_days reads unknown 12h ago
Count business days between two Australian calendar dates for a specified state or territory. Boundary inclusion is explicit so agents do not have to guess the counting rule.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "start_date", "end_date", "state" ], "properties": { "state": { "enum": [ "ACT", "NSW", "NT", "QLD", "SA", "TAS", "VIC", "WA" ], "type": "string", "description": "Australian state or territory" }, "end_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "End date in YYYY-MM-DD format" }, "start_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Start date in YYYY-MM-DD format" }, "include_end_date": { "type": "boolean", "description": "Whether to count the end date. Defaults to true." }, "include_start_date": { "type": "boolean", "description": "Whether to count the start date. Defaults to false." } } }arguments 43 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf3e00dbfc5fc7cc6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f3e00dbfc5fc7cc6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f3e00dbfc5fc7cc6?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 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.