Biohotspot is answering right now. Last checked 7 min ago. It exposes 12 tools.
Ocean data for any coast or sea, Australian marine park facts and Marxan reserve design.
Uptime history
70 hours of history
70 hours agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
1159 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Biohotspot every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add biohotspot --transport http https://biohotspot.ai4wa.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://biohotspot.ai4wa.com/mcp~/.codex/config.toml
[mcp_servers.biohotspot]
url = "https://biohotspot.ai4wa.com/mcp".cursor/mcp.json
{
"mcpServers": {
"biohotspot": {
"url": "https://biohotspot.ai4wa.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"biohotspot": {
"type": "http",
"url": "https://biohotspot.ai4wa.com/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
project
add_project_data
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.
get_project
Get one of your projects: its area (GeoJSON), its data check (each data type covered, partial or missing) and your role. Read-only.
list_project_data
List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.
look
look_here
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.
look_in_area
List every Biohotspot map layer with data inside a polygon on the sea, with a few values from each. Read-only.
features
get_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.
layers
find_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.
marine
get_marine_park
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.
papers
search_papers
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.
projects
list_projects
List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.
simulate
simulate
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.
understand
understand_area
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://biohotspot.ai4wa.com/mcp | streamable-http | answering | 1195 ms | 7 min ago |
Alternatives to Biohotspot
same job, measured the same wayIp Australia
by pipeworx-io
ip-australia -- Australian patent, trade mark and design search, plus patent legal status, from IP…
UI Design to Code
by kinglions
Design-to-code artifact pipeline for UI screenshots, Figma node data, and visual review.
Au Eli MCP
by matematicsolutions
MCP server for Australia's Federal Register of Legislation: search and cite Commonwealth Acts.
Parallel Task MCP
by parallel
An MCP server for deep research or task groups
Dicker Data
by wyre-ai
MCP server for Dicker Data's B2B partner/reseller REST API — pricing, orders, and invoices.
Auspost MCP
by mrfentmen
MCP server for Australia Post: shipments, labels, order tracking and delivery updates.
Bio-Data Parser
by evozim
Bioinformatics and genomic sequence parser for clinical research.
Brandfetch
by brandfetch
Search brands and retrieve design assets, company data, other brand context from Brandfetch's API
Biohotspot — questions
Answers built from our own checks of this server.
What can Biohotspot do?
It exposes 12 tools, read directly from the server on our last check. Among them: add_project_data, find_layers, get_features, get_marine_park, get_project, list_project_data and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Biohotspot mostly used for?
Its tools cluster around project and look. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Biohotspot working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1159 ms. The bar chart above shows every period we have measured.
How do I connect Biohotspot?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Biohotspot need an API key?
No. Biohotspot completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Biohotspot?
It answers our handshake in 1159 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.