io.github.resuly/daleads-mcp
PYPI · DALEADS-MCP
Australian development application and property intelligence data for AI agents.
Available components
Last scanned (11 hours ago)
Scores higher than 93% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to resuly/daleads-mcp). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 65 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1749 tokens (~116/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 1 Nov 26 +14
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 0
- Package version: 0.1.0 → 0.2.0 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 0
- Package version: 0.1.0 → 0.2.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/daleads-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | resuly/daleads-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/resuly/daleads-mcp/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 2645858783 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f6149ab64e5c34b825a9141a45218da0f671e0307c4def7d8be1c8eb79302ff1 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_da ~38
Get full details of a specific development application by ID. Args: da_id: The DA record ID
| Name | Type | Req | Description |
|---|---|---|---|
| da_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_project ~42
Get one rights-cleared canonical project and its linked applications. Args: project_uid: Stable canonical project identifier from search_projects
| Name | Type | Req | Description |
|---|---|---|---|
| project_uid | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_project_changes ~128
Read redacted, rights-cleared event notifications for one project. Persist ``meta.cursor`` after every response. ``meta.next_cursor`` is only the immediate continuation when the current response has another page. Args: project_uid: Stable canonical project identifier since: Optional ISO-8601 lower bound for the first request cursor: Non-negative continuation cursor returned by the API limit: Results per response (default 50, max 100)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| project_uid | string | yes | – |
| since | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_stats ~25
Get overall DA statistics: total records, by state, by category, date range.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_categories ~43
List all trade categories with record counts. Returns categories like: Renovation / Extension, Swimming Pool / Spa, Granny Flat / Secondary Dwelling, Demolition, etc.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_councils ~41
List councils with state, DA count, and last activity date. Args: limit: Max councils to return
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
nearby_das ~166
Find development applications near a location. Args: lat: Latitude lng: Longitude radius_km: Search radius in km (default 5, max 50) category: Filter by trade category since: Only show DAs lodged on or after this ISO date (YYYY-MM-DD) status_group: Normalized status: pending, advertised, approved, rejected, or other page: Page number (default 1) limit: Results per page (max 100)
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lng | number | yes | – |
| page | integer | – | – |
| radius_km | number | – | – |
| since | – | – | – |
| status_group | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
nearby_projects ~151
Find canonical development projects near a WGS84 point. Args: lat: Latitude in WGS84 decimal degrees lng: Longitude in WGS84 decimal degrees radius_km: Search radius in kilometres (default 5, max 200) stage: Optional normalized lifecycle stage project_type: Optional normalized project type page: Page number (default 1) limit: Results per page (default 20, max 100)
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| limit | integer | – | – |
| lng | number | yes | – |
| page | integer | – | – |
| project_type | – | – | – |
| radius_km | number | – | – |
| stage | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
property_flood_sample ~58
Real flood score component example, no API key required. Returns the production scores.flood block for a study-covered Rocklea QLD point: official 1% AEP modelled depth, overlay status, terrain context and provenance.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
property_intelligence ~219
Full property intelligence profile for one Australian address (or lat/lng point). Returns planning (zones, overlays, heritage), hazards (flood, bushfire), environment, transport, nearby DAs, points of interest and scored risk components for the address. Requires an API key on a Property Intelligence plan; each lookup counts toward the key's monthly quota, except the sandbox addresses from property_sandbox_addresses which are never metered. No key? Use property_sample for a complete keyless example first. Args: address: Free-text address, e.g. "34 Mary St Clayton VIC" lat: Latitude (alternative to address) lng: Longitude (alternative to address) components: Optional comma-separated subset to return, e.g. "scores.noise,hazards,das". Blocks: das, poi, planning, hazards, environment, transport, utilities, administrative, public_housing, scores.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| components | – | – | – |
| lat | – | – | – |
| lng | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
property_sample ~56
Complete real Property Intelligence response, no API key required. Returns the canned production payload for 163 Grattan St, Carlton VIC (heritage terrace with DA activity) so you can inspect the full response shape before requesting a key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
property_sandbox_addresses ~51
List sandbox addresses whose lookups never count toward your quota. Twelve real addresses covering all eight states; use them with property_intelligence to evaluate live responses for free on any Property Intelligence key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_das ~229
Search development applications with filters. Args: state: Filter by state (NSW, VIC, QLD, SA, WA, TAS, NT, ACT) council: Filter by council name (e.g. "City of Melbourne") category: Filter by trade category (e.g. "Renovation / Extension", "Swimming Pool / Spa") suburb: Filter by suburb name postcode: Filter by exact postcode since: Only show DAs lodged on or after this ISO date (YYYY-MM-DD) status_group: Normalized status: pending, advertised, approved, rejected, or other is_residential: Filter residential (true) or commercial (false) page: Page number (default 1) limit: Results per page (max 100)
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| council | – | – | – |
| is_residential | – | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| postcode | – | – | – |
| since | – | – | – |
| state | – | – | – |
| status_group | – | – | – |
| suburb | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_projects ~188
Search canonical development projects and their current lifecycle state. Project Intelligence joins related applications and changes into one project. The API only returns rights-cleared evidence and fields. Availability is determined by the API key's server-side Project Intelligence entitlement. Args: q: Project name search, or an exact project_uid state: Australian state or territory code stage: Normalized lifecycle stage exposed by the Project API project_type: Normalized project type exposed by the Project API changed_since: Only projects changed since this ISO-8601 timestamp page: Page number (default 1) limit: Results per page (default 20, max 100)
| Name | Type | Req | Description |
|---|---|---|---|
| changed_since | – | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| project_type | – | – | – |
| q | – | – | – |
| stage | – | – | – |
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sql_query ~192
Run a read-only SQL query against DA records. Pro plan only. Query the 'das' table with columns: id, address, address_suburb, address_postcode, council_name, council_reference, state, trade_category, sub_category, application_type, is_residential, lodgement_date, status, cost_of_development, decision_date, decision_status, on_notice_from, on_notice_to, number_of_dwellings, lot_count, land_use, building_type, storeys, latitude, longitude, data_source, date_fetched, documents, info_url. Description and summary are deliberately unavailable because council free text may contain personal contact details. Max 1000 rows. 10 second timeout. SELECT only. Args: query: SQL SELECT query using table name 'das' params: Optional parameters for %s placeholders
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.resuly/daleads-mcp server?
io.github.resuly/daleads-mcp runs locally as a PyPI package, launched with uvx daleads-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · daleads-mcp
claude mcp add resuly-daleads-mcp -- uvx daleads-mcp
What is the io.github.resuly/daleads-mcp server?
io.github.resuly/daleads-mcp is listed in the public MCP registry as io.github.resuly/daleads-mcp. Australian development application and property intelligence data for AI agents. This page covers its PyPI package (daleads-mcp).
Is the io.github.resuly/daleads-mcp server safe to use?
io.github.resuly/daleads-mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.resuly/daleads-mcp server expose?
io.github.resuly/daleads-mcp exposes 15 tools: search_das, get_da, nearby_das, search_projects, get_project, and 10 more. Their descriptions and schemas cost roughly 1,627 tokens of context every time the server is loaded.
Is the io.github.resuly/daleads-mcp server still maintained?
io.github.resuly/daleads-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.resuly/daleads-mcp server?
VerifyMCP ran 16 checks on io.github.resuly/daleads-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.