AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server
ai.alphaquantlabs/propertycheckalphaquantlabs.aistreamable-httpv1.15.3Scanned
Gold Coast & Brisbane: the building, the street at its door and the everyday context around it.
2 tools: 1 can delete or cancel things and 1 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server can do
The AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server is published by alphaquantlabs.ai, a domain the MCP Registry verified. It has 2 tools. It can delete or cancel things (1 tool: get_full_report) and create or change data (1 tool: check_address). None of its tools only reads.
2 tools bring in text other people can write (check_address and get_full_report).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 1.15.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Deletes or cancels 1Claude Code: deny
get_full_reportFull structured PropertyCheck JSON (propertycheck/2) for one covered address: identity, coverage, capabilities, a summary and up to twelve sections, with status and source details …Reads text others write1 finding
Why it is in this group
- The name "get_full_report" says "get": a word for reading.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "get_full_report" destructive (destructiveHint: true), and its name says "get", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true,"openWorldHint":true}; The name "get_full_report" says "get": a word for reading.
Description, as the server wrote it Full structured PropertyCheck JSON (propertycheck/2) for one covered address: identity, coverage, capabilities, a summary and up to twelve sections, with status and source details where available. Call after check_address shows a full report is available. Free vs paid: check_address returns at most five findings and two unverified items; this tool returns the full sections listed in sections_available (for example hazards, roads and traffic, parking and access, mobility, planning, education and area), each item with its own status. No account or API key is required for one-off purchase: x402 returns a standard PaymentRequired (A$1.39 incl. GST); retry the same call with params._meta['x402/payment']. Coverage is checked before any charge, an address outside coverage is never charged, and retrying with the same idempotency_key or the same payment never charges twice. If the user has no wallet, ask for explicit agreement to the A$4.95 card price, then call the same tool with payment_method='card'; give checkout_url only to the human and poll this same tool with the returned purchase_id and access_token. Never create a second checkout for that purchase. Existing B2B API-key accounts remain supported. After an API-key or x402 purchase, pass report_id instead of address to re-view the same report at zero cost; x402 re-view also carries the original payment proof. Optional sections limits the output; detail='full' restores heavy enumerations from the same stored report, with no second charge.
Annotations the server declares
- title: Get the full PropertyCheck report
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 1Claude Code: ask
check_addressFREE, no key.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it FREE, no key. Use when you have one specific street address in the City of Gold Coast or Brisbane City (Queensland, Australia) and need to understand the property and what surrounds it before renting, buying, relocating, working or studying there. Returns coverage and a short summary: up to five findings and up to two items that could not be verified, each with a status; source where available. Depending on the address and available evidence, findings may cover hazards or planning. Brisbane findings may include the street and its traffic, parking, frontage or road-reserve context, or parent-building height where verified. Gold Coast free checks do not promise paid-only physical context, including frontage, carriageway width, parking or building measurements. Any suburb of those two councils works, for example Surfers Paradise, Robina, Coomera, Kangaroo Point, New Farm or Chapel Hill. Addresses elsewhere are reported as outside coverage. Not for listing search, valuations, mortgages or price forecasts. The answer is a summary only; commercial.full_report.sections_available lists which report sections the full report holds for that address. Never charges.
Annotations the server declares
- title: Check a Gold Coast or Brisbane address (free)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://agents.alphaquantlabs.ai/v1/mcp: tools/list returned 2 tools to an anonymous client, including get_full_report (destructive), check_address (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnget_full_report
The server marks "get_full_report" destructive (destructiveHint: true), and its name says "get", a word for reading.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":true,"openWorldHint":true}; The name "get_full_report" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:check_addressChanges thingsdescriptioninputSchema
- Changed:get_full_reportDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 1.15.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http propertycheck https://agents.alphaquantlabs.ai/v1/mcpclaude mcp add --transport http propertycheck https://agents.alphaquantlabs.ai/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__propertycheck__check_address"
],
"deny": [
"mcp__propertycheck__get_full_report"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as propertycheck. Review it before you use it.
Capability tags behind 2 rules
- mcp__propertycheck__check_address untrusted-input
- mcp__propertycheck__get_full_report untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.alphaquantlabs/propertycheck/verify?hash=a643363e9a6bed687431095c45ce27c3f17f80cf14f4a29a9e0a37584707d263" | jq -e '.changed == false'Pinned hash a643363e9a6b, from Nov 14, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.alphaquantlabs/propertycheck/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.alphaquantlabs/propertycheck)Source: MCP Registry. Synced Nov 1, 2026, 07:17 UTC.
AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: get_full_report.
Can the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server have?
- 2 tools: 1 destructive, 1 write. get_full_report and check_address.
Does the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AQL PropertyCheck — check one exact address (Gold Coast & Brisbane) MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.