Biohotspot

io.github.PascalSun/biohotspotVersion 0.9.0

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

Status

Responds988 msNov 14, 2026, 14:41 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:41 UTC
Latency: 988 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://biohotspot.ai4wa.com/mcpResponds988 msNov 14, 2026, 14:41 UTC

No sign-in

Claude Code

claude mcp add --transport http biohotspot https://biohotspot.ai4wa.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: biohotspot
Remote MCP server URL: https://biohotspot.ai4wa.com/mcp

Cursor

{
  "mcpServers": {
    "biohotspot": {
      "url": "https://biohotspot.ai4wa.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"biohotspot","type":"http","url":"https://biohotspot.ai4wa.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

31 tools

Tools of Biohotspot
	Description		Read-only	Idempotent	Open world
`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.	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.	No	No	Not declared	Yes
`compare_runs`Compare a scenario's kept runs (up to 50, newest first): for each, the targets met, area and cost of the best solution and its settings, ranked best first (most targets met, then lowest cost, then smallest area), with why each other run ranks lower. Read-only.	Compare a scenario's kept runs (up to 50, newest first): for each, the targets met, area and cost of the best solution and its settings, ranked best first (most targets met, then lowest cost, then smallest area), with why each other run ranks lower. Read-only.	No	Yes	Not declared	No
`create_project`Create a Biohotspot project of yours for an area on the sea: a name and a GeoJSON polygon. Biohotspot then runs its data check (what data covers the area). Side effect: adds a project you own; nothing else changes. Needs a verified sign-in.	Create a Biohotspot project of yours for an area on the sea: a name and a GeoJSON polygon. Biohotspot then runs its data check (what data covers the area). Side effect: adds a project you own; nothing else changes. Needs a verified sign-in.	No	No	Not declared	No
`delete_scenario`Permanently delete one of your own saved scenarios and the runs kept with it, as the website's delete does. It cannot be undone. Only the person who saved a scenario can delete it; projects and their data cannot be deleted with these tools. Tell the user the scenario's name and ask them to confirm before calling it.	Permanently delete one of your own saved scenarios and the runs kept with it, as the website's delete does. It cannot be undone. Only the person who saved a scenario can delete it; projects and their data cannot be deleted with these tools. Tell the user the scenario's name and ask them to confirm before calling it.	Yes	No	Not declared	No
`email_report`Email a scenario's PDF report to up to 10 people with a link to the scenario, in your name (replies reach you), as the website's Share report does. Side effect: an email is sent. Confirm the addresses with the user first.	Email a scenario's PDF report to up to 10 people with a link to the scenario, in your name (replies reach you), as the website's Share report does. Side effect: an email is sent. Confirm the addresses with the user first.	No	No	Not declared	Yes
`find_layers`Find Biohotspot map layers by words (e.g. 'seagrass', 'coral bleaching') among its 1,600+ world layers. Returns ids, names and categories (25 by default), and whether each can be read with get_features: only layers whose licence lets Biohotspot share their features are (the others still show in look_here and look_in_area). Also finds the Exmouth Gulf example project's open layers (exmouth_…). Read-only.	Find Biohotspot map layers by words (e.g. 'seagrass', 'coral bleaching') among its 1,600+ world layers. Returns ids, names and categories (25 by default), and whether each can be read with get_features: only layers whose licence lets Biohotspot share their features are (the others still show in look_here and look_in_area). Also finds the Exmouth Gulf example project's open layers (exmouth_…). Read-only.	No	Yes	Not declared	No
`finish_upload`Finish a file added to a project (list_project_data shows those waiting): say what it is (title, source, year, licence: cc-by, cc0, cc-by-nc, other-open, restricted or unsure; item = the data-check item it fills), match its columns (`mapping`, {field: column}, e.g. {"scientificName": "species"}), run Biohotspot's checks and, unless accept is false, use it so it shows on the map and counts in the data check. What is not given keeps its current value. Returns the check's verdict. Needs owner or editor rights.	Finish a file added to a project (list_project_data shows those waiting): say what it is (title, source, year, licence: cc-by, cc0, cc-by-nc, other-open, restricted or unsure; item = the data-check item it fills), match its columns (`mapping`, {field: column}, e.g. {"scientificName": "species"}), run Biohotspot's checks and, unless accept is false, use it so it shows on the map and counts in the data check. What is not given keeps its current value. Returns the check's verdict. Needs owner or editor rights.	No	No	Not declared	No
`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). Give an id that find_layers marks get_features: true. Read-only.	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). Give an id that find_layers marks get_features: true. Read-only.	No	Yes	Not declared	No
`get_habitat`Get one habitat across Australia's marine parks, as its Biohotspot page shows it: the parks that hold it with their figures, sources and the page's address. Give its id from list_habitats or part of its name. Read-only.	Get one habitat across Australia's marine parks, as its Biohotspot page shows it: the parks that hold it with their figures, sources and the page's address. Give its id from list_habitats or part of its name. Read-only.	No	Yes	Not declared	No
`get_layer_years`How many features of a world map layer fall in each year (for layers with dates, such as sightings or bleaching surveys): the series the map's year slider draws. Give a find_layers id. Read-only.	How many features of a world map layer fall in each year (for layers with dates, such as sightings or bleaching surveys): the series the map's year slider draws. Give a find_layers id. Read-only.	No	Yes	Not declared	No
`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.	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.	No	Yes	Not declared	No
`get_project`Get one of your projects: its area's bounding box and size, its data check (each data type covered, partial or missing, with the best layer found) and your role. full=true adds the boundary as GeoJSON and every layer found. Read-only.	Get one of your projects: its area's bounding box and size, its data check (each data type covered, partial or missing, with the best layer found) and your role. full=true adds the boundary as GeoJSON and every layer found. Read-only.	No	Yes	Not declared	No
`list_habitats`List the habitats Biohotspot measures across Australia's marine parks (mangroves, the modelled kelp forest biome and tidal marshes, for now): each one's id, name, how many parks hold it and whether it has a page. Read-only.	List the habitats Biohotspot measures across Australia's marine parks (mangroves, the modelled kelp forest biome and tidal marshes, for now): each one's id, name, how many parks hold it and whether it has a page. Read-only.	No	Yes	Not declared	No
`list_project_data`List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.	List the data a project's team added, with each file's status (receiving, checked, ready, failed). Read-only.	No	Yes	Not declared	No
`list_projects`List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.	List your Biohotspot projects and the ones shared with you: name, area, your role and how complete their data is. Read-only.	No	Yes	Not declared	No
`list_public_projects`List Biohotspot's public projects, the worked examples first: name, area and how complete their data is, and whether each is already in your list. Read-only.	List Biohotspot's public projects, the worked examples first: name, area and how complete their data is, and whether each is already in your list. Read-only.	No	Yes	Not declared	No
`list_scenarios`List the scenarios saved by you and by the teams of your projects (or one project's, with project_id): name, project, who saved it and its last run's headline numbers. Read-only.	List the scenarios saved by you and by the teams of your projects (or one project's, with project_id): name, project, who saved it and its last run's headline numbers. Read-only.	No	Yes	Not declared	No
`load_public_project`Add a public project (list_public_projects) to your list, view only, to look at and plan in it. Side effect: it appears in your project list; nothing else changes.	Add a public project (list_public_projects) to your list, view only, to look at and plan in it. Side effect: it appears in your project list; nothing else changes.	No	No	Not declared	No
`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 its nearest few items each. Read-only. Use it to learn what a place holds; give `layer` (an id from the answer) for that layer in full.	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 its nearest few items each. Read-only. Use it to learn what a place holds; give `layer` (an id from the answer) for that layer in full.	No	Yes	Not declared	No
`look_in_area`List every Biohotspot map layer with data inside a polygon on the sea, with its nearest few items each. Read-only. Give `layer` (an id from the answer) for that layer in full.	List every Biohotspot map layer with data inside a polygon on the sea, with its nearest few items each. Read-only. Give `layer` (an id from the answer) for that layer in full.	No	Yes	Not declared	No
`look_in_project_data`What a project team's own data (their accepted uploads) holds at a point on the sea within `km` (default 1), or inside a polygon: per upload, how many features are there and a few of their names, or a grid's value at the point. Only the data you may see on that project. Read-only.	What a project team's own data (their accepted uploads) holds at a point on the sea within `km` (default 1), or inside a polygon: per upload, how many features are there and a few of their names, or a grid's value at the point. Only the data you may see on that project. Read-only.	No	Yes	Not declared	No
`make_report`Make a PDF report and get a link to it, good for a day: give project_id for the project's data report (what data covers the area, what is missing, the team's files and scenarios) or scenario_id for a scenario report (its habitats against their targets, its kept Marxan runs compared, the best run habitat by habitat). The PDF is built when the link is opened, for the person who asked. Read-only.	Make a PDF report and get a link to it, good for a day: give project_id for the project's data report (what data covers the area, what is missing, the team's files and scenarios) or scenario_id for a scenario report (its habitats against their targets, its kept Marxan runs compared, the best run habitat by habitat). The PDF is built when the link is opened, for the person who asked. Read-only.	No	Yes	Not declared	No
`read_paper`Read a research library document's text, page by page (pages `from_page` to `to_page`, at most 30 at once; default the first 5). Give a document id from search_papers. Documents without a PDF in the library have no pages. Read-only.	Read a research library document's text, page by page (pages `from_page` to `to_page`, at most 30 at once; default the first 5). Give a document id from search_papers. Documents without a PDF in the library have no pages. Read-only.	No	Yes	Not declared	No
`remove_project_from_list`Take a project off your list: a public project you loaded, or a project shared with you, which you then leave (its team must add you again for you to see its team-only data). Your own projects cannot be removed this way. Ask the user before calling it for a shared project.	Take a project off your list: a public project you loaded, or a project shared with you, which you then leave (its team must add you again for you to see its team-only data). Your own projects cannot be removed this way. Ask the user before calling it for a shared project.	Yes	No	Not declared	No
`run_scenario`Run Marxan for one of your saved scenarios with its saved settings (any setting given here replaces the saved one for this run) and keep the run with the scenario, as the website does. Takes a few seconds to a minute; returns the run's summary and each habitat's result. Side effect: adds a run; nothing is overwritten. Only the person who saved the scenario can run it.	Run Marxan for one of your saved scenarios with its saved settings (any setting given here replaces the saved one for this run) and keep the run with the scenario, as the website does. Takes a few seconds to a minute; returns the run's summary and each habitat's result. Side effect: adds a run; nothing is overwritten. Only the person who saved the scenario can run it.	No	No	Not declared	No
`save_scenario`Save a scenario in one of your projects, where its team sees it on the website: a name, an area (a GeoJSON polygon, optional) and Marxan settings that run_scenario then uses. Side effect: adds a scenario; nothing is overwritten or deleted. Needs a verified sign-in and a place on the project's team.	Save a scenario in one of your projects, where its team sees it on the website: a name, an area (a GeoJSON polygon, optional) and Marxan settings that run_scenario then uses. Side effect: adds a scenario; nothing is overwritten or deleted. Needs a verified sign-in and a place on the project's team.	No	No	Not declared	No
`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.	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.	No	Yes	Not declared	No
`share_project`Share one of your projects with a person by email, as an editor or a viewer: Biohotspot emails them a link in your name. Side effect: an email is sent and they join the project's team. Only adds people: someone already on the team keeps their role (change roles on the website). Needs owner or editor rights. Confirm the address with the user first.	Share one of your projects with a person by email, as an editor or a viewer: Biohotspot emails them a link in your name. Side effect: an email is sent and they join the project's team. Only adds people: someone already on the team keeps their role (change roles on the website). Needs owner or editor rights. Confirm the address with the user first.	No	No	Not declared	Yes
`simulate`Run the Marxan optimiser on Biohotspot's planning data (Exmouth Gulf, Western Australia, for now): the cheapest set of planning squares that meets every habitat target. `polygon` protects the squares mostly inside it (unless `protect` is given); the other settings change targets, compactness and what stays open. Takes a few seconds; returns the summary, each habitat's result and the best solution. Nothing is saved: use save_scenario and run_scenario to keep a run in a project.	Run the Marxan optimiser on Biohotspot's planning data (Exmouth Gulf, Western Australia, for now): the cheapest set of planning squares that meets every habitat target. `polygon` protects the squares mostly inside it (unless `protect` is given); the other settings change targets, compactness and what stays open. Takes a few seconds; returns the summary, each habitat's result and the best solution. Nothing is saved: use save_scenario and run_scenario to keep a run in a project.	No	Yes	Not declared	No
`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.	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.	No	Yes	Not declared	No
`update_project`Rename one of your projects or replace its area (a GeoJSON polygon; the data check runs again). Overwrites the old name or area. Needs owner or editor rights; who can see the project is changed on the website only.	Rename one of your projects or replace its area (a GeoJSON polygon; the data check runs again). Overwrites the old name or area. Needs owner or editor rights; who can see the project is changed on the website only.	Yes	No	Not declared	No

Details

Registry status: Active
Published: Nov 13, 2026
Updated: Nov 13, 2026
Website: https://biohotspot.ai4wa.com/tools/marine-data-gis-api⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Files and storageSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing