Biohotspot
REMOTE · BIOHOTSPOT.AI4WA.COM
Ocean data for any coast or sea, Australian marine park facts and Marxan reserve design.
Available components
Last scanned (8 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1281 tokens (~106/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 39% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 73
First indexed and scored.
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 · Probed https://biohotspot.ai4wa.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai4wa.com | CN=YE2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 506e595b26701b08ba5c6f3d268c50e8f2a |
| SANs: *.ai4wa.com, ai4wa.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of biohotspot.ai4wa.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ai4wa.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="biohotspot", resource_metadata="https://biohotspot.ai4wa.com/.well-known/oauth-protected-resource/mcp"
Bearer realm="biohotspot", resource_metadata="https://biohotspot.ai4wa.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Protected resource metadata
| Document | https://biohotspot.ai4wa.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://biohotspot.ai4wa.com/mcp |
| Authorisation server | https://biohotspot.ai4wa.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://biohotspot.ai4wa.com/mcp | Verified | 200 | |
| http (plaintext) | http://biohotspot.ai4wa.com/mcp | HTTPS enforced | 301 | https://biohotspot.ai4wa.com/mcp |
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 →
add_project_data Add data to a project ~184
Add data to a project from a public download link (GeoPackage, zipped Shapefile, GeoJSON, KML, CSV with coordinates or GeoTIFF, up to 200 MB): your own model's output, a survey, a map. Side effect: the file is downloaded, stored and added to the project, where its team can see it; nothing is deleted or overwritten. Biohotspot then checks it; follow its status with list_project_data and finish anything it asks for in the project's Uploads tab. Needs owner or editor rights.
| Name | Type | Req | Description |
|---|---|---|---|
| licence | string | – | cc-by, cc0, cc-by-nc, other-open, restricted or unsure |
| project_id | integer | yes | – |
| source | string | – | Who made it |
| title | string | – | – |
| url | string | yes | – |
| year | integer | – | – |
No output schema declared.
No examples provided.
find_layers Find map layers ~80
Find Biohotspot map layers by words (e.g. 'seagrass', 'coral bleaching') among its 1,600+ world layers. Returns ids, names, categories and licences (25 by default); vector layers can then be read with get_features. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
get_features Read a layer's features ~102
Get a vector layer's features as GeoJSON from Biohotspot's OGC API, optionally inside a bounding box [west, south, east, north]; up to `limit` features (500 by default, 5,000 at most). Collection ids: find_layers ids, or exmouth_<dataset> for the example project's open layers. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | array | – | – |
| collection | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_marine_park Australian marine park facts ~158
Get the facts about an Australian marine park from its Biohotspot page: area, IUCN categories and named zones (CAPAD 2024), habitats, blue carbon and pressures measured inside it, each with its source and licence, and the page's address. Give part of the park's name; `state` (wa, qld, nsw, vic, sa, tas, nt, com for Commonwealth waters) narrows it. Several matches return the list to choose from; parks under 10 km² or without enough open data have no page. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Park name or part of it, e.g. 'Ningaloo' |
| state | string | – | – |
No output schema declared.
No examples provided.
get_project Read a project ~48
Get one of your projects: its area (GeoJSON), its data check (each data type covered, partial or missing) and your role. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | – |
No output schema declared.
No examples provided.
list_project_data Read a project's data ~43
List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | – |
No output schema declared.
No examples provided.
list_projects List your projects ~37
List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
look_here Look at a place ~121
List every Biohotspot map layer with data within `km` of a point on the sea (a place being studied, not the user's location): habitats, wildlife, human uses, protected areas and world ocean maps, with a few values from each. Read-only. Use it to learn what a place holds.
| Name | Type | Req | Description |
|---|---|---|---|
| km | number | – | Radius in km (default 5) |
| lat | number | yes | Latitude of the place to look at, WGS84 |
| lon | number | yes | Longitude of the place to look at, WGS84 |
No output schema declared.
No examples provided.
look_in_area Look inside an area ~50
List every Biohotspot map layer with data inside a polygon on the sea, with a few values from each. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| polygon | object | yes | A GeoJSON Polygon (WGS84) |
No output schema declared.
No examples provided.
search_papers Search the research library ~73
Search Biohotspot's research library (more than 5,200 papers and reports on coasts and marine habitats) for the words; returns titles, years and DOI links where known (10 by default, 50 at most). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
simulate Run the protection options (Marxan) ~129
Run the Marxan optimiser on the example project's planning data (Exmouth Gulf, Western Australia only): the cheapest set of planning squares that meets every habitat target. `protect` = planning-square ids always included (understand_area returns them as `pus`); `target_pct` = one target for every habitat, in %. Takes a few seconds; returns the summary, each habitat's result and the best solution. Nothing is saved to your projects.
| Name | Type | Req | Description |
|---|---|---|---|
| protect | array | – | – |
| reps | integer | – | Runs, 1-20 (default 5) |
| target_pct | number | – | – |
No output schema declared.
No examples provided.
understand_area Check an area against its targets ~141
Check an area against its protection targets: which habitats it holds, how much of each, what is already protected, and how far each habitat is from its target. Give a polygon, or a point and radius_km. Outside Biohotspot's local planning data the answer comes from world maps and is marked rough: true. Read-only; nothing is saved.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitude of the place to look at, WGS84 |
| lon | number | – | Longitude of the place to look at, WGS84 |
| polygon | object | – | A GeoJSON Polygon (WGS84) |
| radius_km | number | – | – |
No output schema declared.
No examples provided.
How do I install the Biohotspot MCP server?
Biohotspot is a hosted endpoint at https://biohotspot.ai4wa.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · biohotspot.ai4wa.com
claude mcp add --transport http pascalsun-biohotspot 'https://biohotspot.ai4wa.com/mcp'
What is the Biohotspot MCP server?
Biohotspot is an MCP server listed in the public MCP registry as io.github.PascalSun/biohotspot. Ocean data for any coast or sea, Australian marine park facts and Marxan reserve design. This page covers its hosted endpoint (https://biohotspot.ai4wa.com/mcp).
Is the Biohotspot MCP server safe to use?
Biohotspot scores 76 out of 100 on VerifyMCP. 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 Biohotspot MCP server expose?
Biohotspot exposes 12 tools: look_here, look_in_area, understand_area, simulate, find_layers, and 7 more. Their descriptions and schemas cost roughly 1,166 tokens of context every time the server is loaded.
Does the Biohotspot MCP server require authentication?
Yes. Biohotspot asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Biohotspot MCP server still maintained?
Biohotspot 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.