AQL PropertyCheck — Gold Coast Property Intelligence API
ai.alphaquantlabs/propertycheck · 1.11.1
Gold Coast property intelligence and due diligence for AI agents, renters and buyers.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://agents.alphaquantlabs.ai/v1/mcpstreamable-httpAuthorizationoptional, secret: Optional for FREE property_coverage and A$1.39 x402 property_report_one_off. Credit/account tools require Bearer <api_key>; create one with POST /v1/accounts. property_report_card_checkout and propert
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 6 tools.
- Protocol
- 2025-06-18
- Calls itself
- aql-propertycheck 1.6.6
- Handshake time
- 1051 ms
- HTTP status
- 200
The tools it lists (6, as of 7 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
property_coverageUse this first to check whether a Gold Coast property or address is supported before buying or renting. Free and returns coverage only, not paid property intelligence. It checks one coordinate in or near the City of Gold Coast. If supported is true, call property_report with the same coordinates and a stable request_id; otherwise stop because unsupported points are never charged. Example: latitude=-27.9675, longitude=153.4136.
property_reportUse this to check a Gold Coast property or address before buying or renting. Call it after property_coverage returns supported=true, with latitude, longitude and a caller-stable request_id. It creates and stores one complete structured JSON report covering the property, everyday life around the address, local risks and mapped changes. One paid lookup returns the full available PropertyCheck package for that address; no multiple property-data calls are required. This is not a valuation or investment forecast. It costs one credit; retrying the same request_id does not charge twice. Every data bl
property_report_getRetrieve an already-paid immutable PropertyCheck report using the report_id returned by property_report. Free; returns the caller-owned stored report, performs no new provider lookup and does not spend another credit. Use this instead of property_report when the report already exists; another organisation's report is never returned. Example: report_id='rpt_abc123'.
propertycheck_lookupDeprecated compatibility alias; do not use for new workflows. Flood, bushfire, transport noise, major electricity infrastructure, planning zone, land use, school catchments, nearest public transport, police division and measured traffic for one point inside current PropertyCheck coverage. Costs one credit. Refused, and not charged for, outside the serviced area. Example: latitude=-27.9675, longitude=153.4136. For new property checks, use property_coverage first, then property_report.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.alphaquantlabs/propertycheck, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 6 hours ago. The registry entry · agents.alphaquantlabs.ai