# Biohotspot (remote · biohotspot.ai4wa.com)

Ocean data for any coast or sea, Australian marine park facts and Marxan reserve design.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `biohotspot.ai4wa.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/pascalsun-biohotspot/biohotspot.md), [page](https://verifymcp.io/servers/pascalsun-biohotspot/biohotspot)

## Channel facts

- Endpoint: `https://biohotspot.ai4wa.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1281 tokens (~106/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 39% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http pascalsun-biohotspot 'https://biohotspot.ai4wa.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pascalsun-biohotspot": {
      "url": "https://biohotspot.ai4wa.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pascalsun-biohotspot": {
      "type": "http",
      "url": "https://biohotspot.ai4wa.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pascalsun-biohotspot]
url = "https://biohotspot.ai4wa.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pascalsun-biohotspot": {
      "type": "remote",
      "url": "https://biohotspot.ai4wa.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pascalsun-biohotspot --url 'https://biohotspot.ai4wa.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pascalsun-biohotspot:
    url: "https://biohotspot.ai4wa.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pascalsun-biohotspot": {
      "Transport": "http",
      "Url": "https://biohotspot.ai4wa.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pascalsun-biohotspot -t streamable-http -u 'https://biohotspot.ai4wa.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pascalsun-biohotspot": {
      "type": "http",
      "url": "https://biohotspot.ai4wa.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +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.

### 2026-11-02 (score 75, +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.

### 2026-11-01 (score 74, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-31 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 73)

First indexed and scored.

## MCP tools (12)

### `look_here` (~121 tokens)

Look at a place

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.

Input parameters:

- `km` (number): Radius in km (default 5)
- `lat` (number, required): Latitude of the place to look at, WGS84
- `lon` (number, required): Longitude of the place to look at, WGS84

### `look_in_area` (~50 tokens)

Look inside an area

List every Biohotspot map layer with data inside a polygon on the sea, with a few values from each. Read-only.

Input parameters:

- `polygon` (object, required): A GeoJSON Polygon (WGS84)

### `understand_area` (~141 tokens)

Check an area against its targets

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.

Input parameters:

- `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)

### `simulate` (~129 tokens)

Run the protection options (Marxan)

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.

Input parameters:

- `protect` (array)
- `reps` (integer): Runs, 1-20 (default 5)
- `target_pct` (number)

### `find_layers` (~80 tokens)

Find map layers

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `get_features` (~102 tokens)

Read a layer's features

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.

Input parameters:

- `bbox` (array)
- `collection` (string, required)
- `limit` (integer)

### `get_marine_park` (~158 tokens)

Australian marine park facts

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.

Input parameters:

- `name` (string, required): Park name or part of it, e.g. 'Ningaloo'
- `state` (string)

### `search_papers` (~73 tokens)

Search the research library

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `list_projects` (~37 tokens)

List your projects

List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.

### `get_project` (~48 tokens)

Read a project

Get one of your projects: its area (GeoJSON), its data check (each data type covered, partial or missing) and your role. Read-only.

Input parameters:

- `project_id` (integer, required)

### `list_project_data` (~43 tokens)

Read a project's data

List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.

Input parameters:

- `project_id` (integer, required)

### `add_project_data` (~184 tokens)

Add data to a project

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.

Input parameters:

- `licence` (string): cc-by, cc0, cc-by-nc, other-open, restricted or unsure
- `project_id` (integer, required)
- `source` (string): Who made it
- `title` (string)
- `url` (string, required)
- `year` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pascalsun-biohotspot/biohotspot#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://biohotspot.ai4wa.com/mcp
- Website: https://biohotspot.ai4wa.com/tools/marine-data-gis-api
- Changelog RSS feed: https://verifymcp.io/servers/pascalsun-biohotspot/biohotspot.xml
- Changelog JSON feed: https://verifymcp.io/servers/pascalsun-biohotspot/biohotspot.json
- HTML version of this page: https://verifymcp.io/servers/pascalsun-biohotspot/biohotspot